The log files are kept by the syslogd/klogd processes. Pull the
appropriate symlinks out of the /etc/rc?.d directories (or edit the
etc/rc.d/rc.? scripts, depending on your distribution) and they won't
be started.
> Is there any way to log to ramdisk, so that corruption does not exist on
> restart?
Yes, just make sure the ramdisk partition is mkfs'd and mounted before
syslogd/klogd are started.
> Better yet, is there some recovery scheme that does not require console
> intervention?
> (apparently the file system check will not run unattended)
You can hack e2fsck... throw in some failure case handlers (like
automatically trying backup superblocks if the primary is invalid,
etc) and throw out any checks to make sure "the user is really
there"... but remember, that stuff is probably there for a reason.
I realize this is an embedded system, but if its networked or has
serial outut it may be a better option to just have syslogd direct all
logging data over the network/serial port/etc. This way you can have
persistent storage of the logs on the far end and won't have to worry
about doing a "proper" shutdown... (man syslogd.conf)
Adam
-- Things look so bad everywhere Adam D. Bradley artdodge@cs.bu.edu In this whole world what is fair Boston University Computer Science We walk blind and we try to see Ph.D. student and Linux hacker Falling behind in what could be ----> Bring me a Higher Love ----> <><
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu