Alternative to syslogd that actually writes external logs to
Adam Vande More
amvandemore at gmail.com
Mon Nov 28 16:10:36 UTC 2011
On Mon, Nov 28, 2011 at 6:58 AM, Kaya Saman <kayasaman at gmail.com> wrote:
> I would like to know if there's a syslog alternative out there that will
> actually write my network equipments' logs to files.
> After having major issues with syslogd and attempting a thorough debug of
> which I posted to this mailing list and wasn't able to fix even with more
> experienced peoples help I am now looking for an alternative!
> My issue with syslogd was the fact that the logging information would be
> sent to my system and that could evidently be seen, however, the software
> didn't write to the log file specified for whatever reason :-(
> During debug I started syslogd using the -d and -vv options, checked the
> log file in question was created and had correct permission. Everything
> seemed fine but nothing even tried to write to file.
> Basically I am looking for just something that will write all my external
> logs to file and can keep syslogd for the system specific logs as that's no
> Since at the time I was using FreeBSD 8.0 CURRENT x64, I upgraded to 8.2
> on the basis that my system and hence ports collection was out-of-date; but
> unfortunately the update didn't solve my issues regarding syslog. - which
> is way odd considering I had FreeBSD 8.1 or 8.2 x86 edition running on an
> old (now packed-up) PIV which did my logging without any issues. - The
> current setup is the same except for the fact that am running Jails and am
> on a 64bit platform.
Properly configured, syslogd will log remotely. However something like
sysutils/rsyslog may fit your requirements better.
Adam Vande More
More information about the freebsd-questions