Questions (logging, etc-updating, date, etc)
Posted: Thu Jul 07, 2005 10:12 pm
Have a few ?'s:
I recently did a decent sized emerge -uD world. Ended up with 100+ etc files to merge and everything went (so it seems) fine except for net.eth0 and net.lo. Those two files seem to have been screwed up somewhat. If I look at the new version of net.eth0, it looks like it should be net.lo (even manually sets to 127.0.0.1 as lo should do). When I look at the new version of net.lo, it's fairly elaborate and does a ton of new things like loading modules and whatnot. I'm not sure if this is a mixup and I don't really want to risk screwing up my network. Anyone recently emerged and found these differences?
Why does the majority of the log messages (shorewall is a large part of em, but many others) get logged to several different files in /var/log/messages. There's syslog, messages and kern.log (at least) that all seem to contain the same logs. Is there something configured wrong or is this just a waste of resources?
Anyone else notice that randomly after a reboot the date is completely out of whack? I've gone to some day in december in 2032, some day in january in 1992, etc. Not sure if it happens only after ungraceful reboots or what, but it's a pain in the ass =)
I recently did a decent sized emerge -uD world. Ended up with 100+ etc files to merge and everything went (so it seems) fine except for net.eth0 and net.lo. Those two files seem to have been screwed up somewhat. If I look at the new version of net.eth0, it looks like it should be net.lo (even manually sets to 127.0.0.1 as lo should do). When I look at the new version of net.lo, it's fairly elaborate and does a ton of new things like loading modules and whatnot. I'm not sure if this is a mixup and I don't really want to risk screwing up my network. Anyone recently emerged and found these differences?
Why does the majority of the log messages (shorewall is a large part of em, but many others) get logged to several different files in /var/log/messages. There's syslog, messages and kern.log (at least) that all seem to contain the same logs. Is there something configured wrong or is this just a waste of resources?
Anyone else notice that randomly after a reboot the date is completely out of whack? I've gone to some day in december in 2032, some day in january in 1992, etc. Not sure if it happens only after ungraceful reboots or what, but it's a pain in the ass =)