[Twisted-Python] Implementing a syslog-deamon ??

[Uwe C. Schroeder]

On Thursday 10 July 2003 02:48 am, Moshe Zadka wrote:
> On Thu, 10 Jul 2003, "Thomas Weholt \( PRIVAT \)" <2002 at weholt.org> wrote:
> > I was wondering if I could implement a fully syslog-compatible
> > syslog-deamon/server using Twisted?
>
> Yes it is. Writing a syslog is not extremely hard.
> [Note that it will probably constrain your mounting order, since syslog
> has to start pretty soon. OTOH, putting /usr/ on a different partition
> than / is an obsolete idea, so that shouldn't be a big problem.]

Not an obsolete idea. Just not too commonly used anymore. Look at large 
mission critical unix deployments and you'll see the split of / /usr /var 
etc. And basically: just fill up your harddrive and see what happens. A lot 
of daemons will stop working. If you have different partitions / will still 
have room for logfiles / configfiles.

> > We need a syslog up and running as soon
> > as possible to let our firewall use it, due to some suspicion about
> > hacking etc.
>
> "As soon as possible" and "implement my own" are usually at odds.
>
> > It would help alot of I could implement a syslog-deamon that put data
> > sent to it into a database, instead of to a file. The server must be able
> > to run on Windows.
>
> Why? What in syslog logs to a a syslog daemon? More importantly, syslog
> relies on unix-specific APIs, IIRC, like named pipes or unix domain pipes.

Nothing in syslog logs to syslog (except you set it up that way). What he is 
trying to do is to receive the log from his firewall which obviously - as do 
most firewalls - provides a syslog facility to send the logs somewhere else ( 
most "out of the box" systems do that due to lack of own harddrive)



	UC

--
Open Source Solutions 4U, LLC	2570 Fleetwood Drive
Phone:  +1 650 872 2425		San Bruno, CA 94066
Cell:   +1 650 302 2405		United States
Fax:    +1 650 872 2417