> My questions: > - What can be done to avoid such problems? Assume > that a forced shutdown can *not* be avoided at all > times - this time, a build-process gone wild was > eating up all memory incl. swap. The system was fully > unresponsive.
Any input to this issue is still appreciated, while... > - This time, "svcs -xv" tells me that two services > fail to start because the inetd service is not > running. However, "svcadm enable > svc:/network/inetd:defaut" does not fix this, nor > does it give me any hint on the console or the log > (/var/svc/log/network-inetd:default.log). ...I could fix this one myself: service "fc-devices" (FibreChannel - I have no fibre channel at all...) needed to be enabled manually. No idea why it had been disabled. Strange. Before, I had to disable the ntp service, but at least it complained about missing /etc/inet/ntp.conf. Again, no idea why it has been enabled as ntp.conf does not exist on any of my boxes. Nevertheless, I don't like the perspective of having to try for hours after each ungraceful shutdown (I am developing kernel modules...). Joachim This message posted from opensolaris.org _______________________________________________ opensolaris-help mailing list [email protected]
