Hi, Good news. The problem with sun-doors are solved: ----- Forwarded message from Balazs Scheidler <bazsi@blurp.balabit.hu> ----- Date: Thu, 17 Jun 1999 22:48:14 +0200 From: Balazs Scheidler <bazsi@blurp.balabit.hu> To: bazsi@balabit.hu Subject: Fwd: Re: Solaris and syslogd Path: news.iif.hu!news.bme.hu!news-ge.switch.ch!newsfeed.berkeley.edu!dispose.news.demon.net!demon!colt.net!easynet-tele!easynet.net!btnet-feed2!btnet!carbon.eu.sun.com!uk-usenet.uk.sun.com!nl-usenet.holland.sun.com!not-for-mail From: Casper.Dik@Holland.Sun.Com (Casper H.S. Dik - Network Security Engineer) Newsgroups: comp.unix.solaris Subject: Re: Solaris and syslogd Date: 15 Jun 1999 07:46:58 GMT Organization: Sun Microsystems, Netherlands Distribution: inet Message-ID: <casper.929432774@nl-usenet.sun.com> References: <slrn7m85qd.2gg.bazsi@blurp.balabit.hu> NNTP-Posting-Host: room101.holland.sun.com Mail-Copies-To: never Lines: 22 [[ PLEASE DON'T SEND ME EMAIL COPIES OF POSTINGS ]] bazsi@blurp.balabit.hu (Balazs Scheidler) writes:

I am writing a portable syslogd replacement, and I have a small problem with Solaris. I hope someone can help me out.

So, the facts I know: Solaris uses the new multithreaded door mechanism to send messages from client programs to the syslogd server. The used door is called /etc/.syslog_door.

No, it doesn't. It uses the msglog device to sendmessages. The syslog door is used to confirm that syslogd is still running. Casper -- Expressed in this posting are my opinions. They are in no way related to opinions held by my employer, Sun Microsystems. Statements on Sun products included here are not gospel and may be fiction rather than truth. ----- End forwarded message ----- -- Bazsi