On Dec 26, 2007, at 9:40 PM, Peter Boosten wrote:
Quoting Livia Markoczy [EMAIL PROTECTED]:
syslog_ng_config=-u daemon
But nothing has logged anywhere, including to console, since the
time I
killed the system syslogd.
file permissions. While your syslog-ng runs as daemon, it has no
Quoting Jeffrey Goldberg [EMAIL PROTECTED]:
Is there any reason not to simply do a
cd /var/log
chown -R daemon .
I think (but I'm not sure) that permissions will be reversed by mtree.
also
chown daemon /dev/console
Won't work either. *if* you're going to do that you should alter
On Dec 27, 2007, at 10:40 AM, Peter Boosten wrote:
Quoting Jeffrey Goldberg [EMAIL PROTECTED]:
Is there any reason not to simply do a
cd /var/log
chown -R daemon .
I think (but I'm not sure) that permissions will be reversed by mtree.
This is the first I've heard of mtree. I just looked
Jeffrey Goldberg wrote:
This is the first I've heard of mtree. I just looked mtree(8), but I
take it that mtree is run periodically somehow to fix things. Do
you know where?
I can always keep my logs in some place other than /var/log if this is
an issue.
IIRC it's done at boot time.
I've just installed syslog-ng from ports on 7.0B4.
I put the following into /etc/rc.conf
syslog_ng_enable=YES
syslog_ng_config=-u daemon
syslog_ng_pid=/var/run/syslog-ng.pid
And my syslog-ng.conf file is very similar to the example one (plus
some special destinations for things that come in
Quoting Livia Markoczy [EMAIL PROTECTED]:
I've just installed syslog-ng from ports on 7.0B4.
I put the following into /etc/rc.conf
syslog_ng_enable=YES
syslog_ng_config=-u daemon
syslog_ng_pid=/var/run/syslog-ng.pid
And my syslog-ng.conf file is very similar to the example one (plus
some
