> -----Original Message----- > From: Marc Thomas [mailto:[EMAIL PROTECTED]] > Sent: Friday, December 20, 2002 1:01 PM > To: James-lists > Subject: RE: syslog server- how to on Linux > > > I also have to agree. > > I went through this very issue when building my firewall machine. > I wanted specific logging and looked into syslogd to make some > changes. a simple "man syslogd" wasn't enough to tell me what I > was looking for. While it described configuring syslog, and it's > function, it didn't adequately describe each syslog facility such > as "auth" "kern" "debug" and so on, and what each facility was > responsible for logging. In my case, man pages for syslog in > sections 2 and 3 weren't even installed on the system. Only after > extensive googling did I find what I wanted, which really wasn't > of much help. So in some cases, a simple "man 'something'" isn't > always the best answer. > > In the end I went with syslog-ng http://www.balabit.hu/en/downloads/syslog-ng/ which proved far more flexible and with better documentation. So far, it has worked out very well.
My $0.02 Marc > -----Original Message----- > From: James-lists [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 18, 2002 4:07 PM > To: [EMAIL PROTECTED] > Subject: Re: syslog server- how to on Linux > > > > > I use Linux here as well, but I have to contradict you on > this one. The man > > pages (in my opinion) do not explain anything, they merely > remind you of the > > relevant command syntax if you already know what you're > doing. Info pages > > are a bit better, but don't even come close to being > available for most > > commands. > > > Chris Berry > > [EMAIL PROTECTED] > > Systems Administrator > > JM Associates > > > Here, here ! I highly agree. Unless a person is asking for a > specific command or is experienced > saying "Read the man" is of no help. Also, every man page is > different, some are extensive and some are > not. It all depends on who wrote them. > >
