05-18-2014, 11:45 PM
Just an update on a bit of scrounging around I've done...
Some of you probably already know (but I am no techie so it's news to me) that rsyslog is the program that controls all the logging functions I have complained are not working. I read every readable file relating to rsyslog that "find / -name "*rsyslog*" turned up. The only thing suspicious I found in /etc/rsyslog.conf---the instruction to
start on filesystem
stop on runlevel [06]
so I changed the first line to "start on runlevel [2345]" to match the second line's format.
Mostly because there were a number of rsyslog-related files missing (according to the documentations I read), I removed rsyslog and reinstalled it--as well as ubuntu-minimal, which was tied to rsyslog. The re-install restored the missing files but, of course, did not replace the rsyslog.conf file. (I was leery about *purging* ubuntu-minimal, so chose to just remove and then reinstall them.) As a result of being cautious, I may have failed to remove the cause of this problem.
I also discovered that I can use 'logger' to send a message to syslog---which, unfortunately, did not show up in syslog, despite using the priority switch to specifically sending it to "-p syslog.info".
In all, I am no closer to a resolution, but I hopefully have provided some reader with enough information to recognize the issue and suggest a next step. Meanwhile, I'll try burning the Linux Lite .iso to a DVD disk; the tight squeeze onto a CD made the Linux Lite installation run a LOT slower--and my DVD drive work a lot harder--than I expected for an OS of this size. Maybe (fingers crossed!) rsyslog got lost in the shuffle. I'll reinstall the OS from a DVD, see if that makes any difference, and report back.
Some of you probably already know (but I am no techie so it's news to me) that rsyslog is the program that controls all the logging functions I have complained are not working. I read every readable file relating to rsyslog that "find / -name "*rsyslog*" turned up. The only thing suspicious I found in /etc/rsyslog.conf---the instruction to
start on filesystem
stop on runlevel [06]
so I changed the first line to "start on runlevel [2345]" to match the second line's format.
Mostly because there were a number of rsyslog-related files missing (according to the documentations I read), I removed rsyslog and reinstalled it--as well as ubuntu-minimal, which was tied to rsyslog. The re-install restored the missing files but, of course, did not replace the rsyslog.conf file. (I was leery about *purging* ubuntu-minimal, so chose to just remove and then reinstall them.) As a result of being cautious, I may have failed to remove the cause of this problem.
I also discovered that I can use 'logger' to send a message to syslog---which, unfortunately, did not show up in syslog, despite using the priority switch to specifically sending it to "-p syslog.info".
In all, I am no closer to a resolution, but I hopefully have provided some reader with enough information to recognize the issue and suggest a next step. Meanwhile, I'll try burning the Linux Lite .iso to a DVD disk; the tight squeeze onto a CD made the Linux Lite installation run a LOT slower--and my DVD drive work a lot harder--than I expected for an OS of this size. Maybe (fingers crossed!) rsyslog got lost in the shuffle. I'll reinstall the OS from a DVD, see if that makes any difference, and report back.