From: Christopher Faylor <cgf-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Syslog (was: <no subject>)
Date: Mon, 10 Jun 2002 10:22:00 -0000 [thread overview]
Message-ID: <20020610162923.GA14621@redhat.com> (raw)
In-Reply-To: <Pine.CYG.4.44.0206101017180.1968-100000@aca-vnt.mcc.ac.uk>
On Mon, Jun 10, 2002 at 10:24:12AM +0100, Tony Arnold wrote:
>Dear All,
>
>On Mon, 10 Jun 2002, Bjoern Kahl AG Resy wrote:
>
>> On Mon, 10 Jun 2002, Thomas Mellman wrote:
>>
>> > I can't find any reference to syslogd for CYGWIN, although there
>> > is a syslog(1).
>> > Isn't this daemon necessary to write a /var/log/messages file?
>>
>> AFAIK all syslog-messages are send to the NT-syslog-service. I
>> dont know how it is named in the english version of NT, but in
>> the german NT it is named "Ereignisanzeige", so probably "event-viewer"
>> or some thing like that in the english versions of NT.
>
>I recall a question posted by Chris Faylor some time ago asking if the
>community wanted continued support for syslogd in Cygwin. As there was no
>demand for it at the time, the support was dropped.
Huh? We never, AFAIK, supported syslogd. I don't recall ever asking if the
community wanted continued support. I might have asked if anyone had a solution
for Windows 9x, though.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-06-10 16:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-10 2:21 <no subject> Thomas Mellman
2002-06-10 3:07 ` Syslog (was: <no subject>) Bjoern Kahl AG Resy
2002-06-10 3:25 ` Tony Arnold
2002-06-10 7:29 ` Nicholas Wourms
2002-06-10 7:41 ` Corinna Vinschen
2002-06-10 7:46 ` Nicholas Wourms
2002-06-10 8:22 ` Corinna Vinschen
2002-06-10 10:22 ` Christopher Faylor [this message]
2002-06-10 13:15 ` Tony Arnold
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020610162923.GA14621@redhat.com \
--to=cgf-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).