# TREE nightly/rawhide-20051005 # ARCH *all* Was thinking perhaps timestamping /tmp/syslog entries might be useful. Seems like it would be a minimal change, that might proof handy in debugging dhcp/network timeout issues. We already go about timestamping entries in /tmp/anaconda.log. I'm trying to make sense out of doklog() function in loader2/init.c which looks like it forks and sets up a socket to handle the logging? Thoughts?
Yes, doklog handles the logging from the kernel and writes it to /tmp/syslog. It would be pretty trivial to add timestamping here as well. Somewhere on the giant list of things to do is also to add remote syslogging support to the loader to match what the second stage is capable of.
Not going to do this.