Top Document: SGI admin Frequently Asked Questions (FAQ) Previous Document: -92- What's wrong with ftpd in IRIX 5.2? Next Document: -94- I just edited /etc/inittab, and now I can't start up or shut down my SGI! What's wrong? See reader questions & answers on this topic! - Help others by sharing your knowledge Popular causes include: - running out of disk space. Once syslogd is unable to write to /usr/adm/SYSLOG, it won't try again until it is `killall -HUP syslogd`ed. - installing IRIX 4.0.x and failing to heed the nagging from the system when it is rebooted to run 'versions changed' and combine new and old configuration files. In this case, the trouble is in /usr/spool/cron/crontabs/root. - Separating fields in /etc/syslog.conf with spaces instead of tabs. If you use spaces, syslogd will silently segv when it reads that file. User Contributions:Top Document: SGI admin Frequently Asked Questions (FAQ) Previous Document: -92- What's wrong with ftpd in IRIX 5.2? Next Document: -94- I just edited /etc/inittab, and now I can't start up or shut down my SGI! What's wrong? Single Page [ Usenet FAQs | Web FAQs | Documents | RFC Index ] Send corrections/additions to the FAQ Maintainer: sgi-faq@viz.tamu.edu (The SGI FAQ group)
Last Update March 27 2014 @ 02:12 PM
|
Comment about this article, ask questions, or add new information about this topic: