[Bug 794727] Re: Please symlink /var/log/messages to syslog

2013-05-17 Thread Robie Basak
It looks like this bug has a few duplicates and other implications, such as to logwatch in bug 1010625. So I think the original bug should remain, since most comments here pertain to that, and it is useful to keep this bug to help track anything else that has been affected by this change. I have

[Bug 794727] Re: Please symlink /var/log/messages to syslog

2013-05-16 Thread Craig
This bug has adversely affected the LogWatch package. Every service that specifies 'LogFile = messages' in its LogWatch .conf file (there are 40 of them) is now dead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 794727] Re: Please symlink /var/log/messages to syslog

2013-05-04 Thread André Pirard
If you remove /var/log/messages you must also update 13.500.000 Web pages that refer to it. You just can't tell the general user to constantly scrutinize bug comments and update his rsyslog.conf. Unless Ubuntu is only for geeks... -- You received this bug notification because you are a member

[Bug 794727] Re: Please symlink /var/log/messages to syslog

2013-04-30 Thread Dimitri Pappas
Trying to configure my pure-ftpd server which relies on messages, and the log window was empty. I've re-enabled it the way it should be, in rsyslogv conf. /var/log/messages is an essential part of any unix distro. What needs to happen is that the distinction between syslog and messages needs to

[Bug 794727] Re: Please symlink /var/log/messages to syslog

2013-03-08 Thread Mike Neish
Hi Phillip, While I would be happy to see /var/log/messages return in some form, I would be cautious about introducing it as a symlink. What happens if someone has manually re-enabled it through /etc/rsyslog.d/50-default.conf while at the same time a new symlink points from /var/log/messages to