grep inetd /etc/rc?.d/* の結果は、 # grep inetd /etc/rc?.d/* /etc/rc0.d/K42inetsvc: /usr/bin/pkill -x -u 0 'in.named|inetd' /etc/rc0.d/K42inetsvc:# Run inetd in "standalone" mode (-s flag) so that it doesn't have /etc/rc0.d/K42inetsvc:# to submit to the will of SAF. Why did we ever let them change inetd? /etc/rc0.d/K42inetsvc:/usr/sbin/inetd -s & /etc/rc1.d/K42inetsvc: /usr/bin/pkill -x -u 0 'in.named|inetd' /etc/rc1.d/K42inetsvc:# Run inetd in "standalone" mode (-s flag) so that it doesn't have /etc/rc1.d/K42inetsvc:# to submit to the will of SAF. Why did we ever let them change inetd? /etc/rc1.d/K42inetsvc:/usr/sbin/inetd -s & /etc/rc2.d/S72inetsvc: /usr/bin/pkill -x -u 0 'in.named|inetd' /etc/rc2.d/S72inetsvc:# Run inetd in "standalone" mode (-s flag) so that it doesn't have /etc/rc2.d/S72inetsvc:# to submit to the will of SAF. Why did we ever let them change inetd? /etc/rc2.d/S72inetsvc:/usr/sbin/inetd -s & /etc/rc2.d/S72inetsvc~: /usr/bin/pkill -x -u 0 'in.named|inetd' /etc/rc2.d/S72inetsvc~:# Run inetd in "standalone" mode (-s flag) so that it doesn't have /etc/rc2.d/S72inetsvc~:# to submit to the will of SAF. Why did we ever let them change inetd? /etc/rc2.d/S72inetsvc~:/usr/sbin/inetd -s & /etc/rc2.d/S73cachefs.daemon:inetconf=/etc/inet/inetd.conf /etc/rcS.d/K42inetsvc: /usr/bin/pkill -x -u 0 'in.named|inetd' /etc/rcS.d/K42inetsvc:# Run inetd in "standalone" mode (-s flag) so that it doesn't have /etc/rcS.d/K42inetsvc:# to submit to the will of SAF. Why did we ever let them change inetd? /etc/rcS.d/K42inetsvc:/usr/sbin/inetd -s & となります。 本当にすみません。
ちなみに、nfsfindを見ると下記のように書いてあったり # Check shared NFS filesystems for .nfs* files that # are more than a week old. # # These files are created by NFS clients when an open file # is removed. To preserve some semblance of Unix semantics # the client renames the file to a unique name so that the # file appears to have been removed from the directory, but # is still usable by the process that has the file open.
Type control-d to proceed with normal startup; (orgive root password for system maintenance);
と言われるようにまりした。
Ctrl-Dを押しますと表示されます起動メッセージの中に X-server can not be started on display :0... とあります。
その後 NOV12 12:31;49 cssd:starting ccv.sh(pid#363) (pidの値はインクリメントされていきます。) The process"ccv.sh" has been exitend whith retcord #24320 とのメッセージが延々と表示され続けます。
checking for GLIB - version >= 1.2.0... no *** Could not run GLIB test program, checking why... *** The test program compiled, but did not run. This usually means *** that the run-time linker is not finding GLIB or finding the wrong *** version of GLIB. If it is not finding GLIB, you'll need to set your *** LD_LIBRARY_PATH environment variable, or edit /etc/ld.so.conf to point *** to the installed location Also, make sure you have run ldconfig if that *** is required on your system *** *** If you have an old version installed, it is best to remove it, although *** you may also be able to get things to work by modifying LD_LIBRARY_PATH *** *** If you have a RedHat 5.0 system, you should remove the GTK package that *** came with the system with the command *** *** rpm --erase --nodeps gtk gtk-devel configure: error: *** GLIB 1.2.0 or better is required. The latest version of GLIB *** is always available from ftp://ftp.gtk.org/. と出てMakefileが作れません。 glib-config --version で確認しても1.2.0となっているんですが、失敗する原因が僕のレベルじゃ分かりません。 どなたかわかる方がいたら是非教えてください。
717 ：ernest ：01/11/12 15:12
ありがとうございます。PCはunixです。 いろいろやっているうちに取り出しボタンは 反応するようになったのですが、 cd-romを入れても認識されていないようです。 df-kで調べてみてもcd-romに対応しているものはなさそうです。 cd-romからbootするようにしても（boot cdrom) No Device なんて言われてしまいます。 とりあえずejectのパラメータとして /dev/dsk 配下の c0t?d0s? を全部実行したのですが >Inappropriate ioctl for device やら >No such device or address 言われてしまいます。