<no subject>

<no subject>

[Thomas Mellman]

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?

I ask because I'm still trying to get inetd to work, and I've gotten so far:

   $ telnet $(uname -n)
   Trying xxx.xxx.xxx.xxx ...
   Connected to myhost.domain
   Escape character is '^]'.
   Connection closed by foreign host.

and I wanted to try to enable debugging for telnetd in /etc/inet.conf, but I can't
make out where it might be going to.

-- 

----------------
Thomas Mellman
thomas@mellman.net
______________________________________________________________________________
All inclusive! 100 MB Speicher, SMS 50% gunstiger, 32 MB Attachment-Gro?e, 
Preisvorteile und mehr unter http://club.web.de/?mc=021104


--
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/

Re: Syslog (was: <no subject>)

[Bjoern Kahl AG Resy]

 Hello!

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.


 Bjoern

-- 
+---------------------------------------------------------------------+
| Dipl.-Phys. Bjoern Kahl +++ AG Embedded Systems and Robotics (RESY) |
| Informatics Faculty +++ Building 48 +++ University of Kaiserslautern|
| phone: +49-631-205-2654 +++ www: http://resy.informatik.uni-kl.de   |
+---------------------------------------------------------------------+



--
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/

Re: Syslog (was: <no subject>)

[Tony Arnold]

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.

Having thought about it since, I can see some good reasons for having it:

	1) Being able to grep a log file and otherwise process it with
UNIX like tools would be a great advantage. I don't know of anyway to look
at the NT event log using non Windoze tools (and if you could, the
messages are not that friendly).

	2) The ability to send logging to a central syslog server as you
can on UNIX systems would also be useful. We currently centralise our
logging and we than analyse the log to detect attempted intrusion
patterns. extending this to Windows boxes would be very useful.

Just my 2 pen'orth.

Regards,
Tony.
-- 
Tony Arnold, Deputy to the Head of COS Division, Manchester Computing,
University of Manchester, Oxford Road, Manchester M13 9PL.
T: +44 (0)161 275 6093, F: +44 (0)870 136 1004, M: +44 (0)773 330 0039
E-mail: tony.arnold@man.ac.uk, Home: http://www.man.ac.uk/Tony.Arnold


--
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/

Re: Syslog (was: <no subject>)

[Nicholas Wourms]

--- Tony Arnold <tony.arnold@man.ac.uk> wrote:
> 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.
> 
> Having thought about it since, I can see some good reasons for having
> it:
> 
> 	1) Being able to grep a log file and otherwise process it with
> UNIX like tools would be a great advantage. I don't know of anyway to
> look
> at the NT event log using non Windoze tools (and if you could, the
> messages are not that friendly).

This would be a definite plus in that catagory!

> 
> 	2) The ability to send logging to a central syslog server as you
> can on UNIX systems would also be useful. We currently centralise our
> logging and we than analyse the log to detect attempted intrusion
> patterns. extending this to Windows boxes would be very useful.
> 

I completely agree, plus it could also allow customization of which
messages are logged and which are sent to the console.

So you have my vote for this functionality :-).

Cheers,
Nicholas

__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

--
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/

Re: Syslog (was: <no subject>)

[Corinna Vinschen]

On Mon, Jun 10, 2002 at 05:47:18AM -0700, Nicholas Wourms wrote:
> I completely agree, plus it could also allow customization of which
> messages are logged and which are sent to the console.
> 
> So you have my vote for this functionality :-).

There's just the problem that we don't want Cygwin to rely on
a running syslogd.  syslogd isn't an integral part of the OS
(as on U*X systems) while the NT event log is.  Well, on NT.
On 9x we have the ugly syslog file workaround.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
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/

Re: Syslog (was: <no subject>)

[Nicholas Wourms]

--- Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
> On Mon, Jun 10, 2002 at 05:47:18AM -0700, Nicholas Wourms wrote:
> > I completely agree, plus it could also allow customization of which
> > messages are logged and which are sent to the console.
> > 
> > So you have my vote for this functionality :-).
> 
> There's just the problem that we don't want Cygwin to rely on
> a running syslogd.  syslogd isn't an integral part of the OS
> (as on U*X systems) while the NT event log is.  Well, on NT.
> On 9x we have the ugly syslog file workaround.
> 
> Corinna
Corinna,

If you are going to emulate *n*x, you are going have to run some
processes.  Memory is cheap, and certainly the syslogd wouldn't use that
much, would it?  Also, it's not like you couldn't have the messages fall
back to the NTeventlog or Ugly-syslog, should the service not be started
or fail.  I bet it would even be possible to have syslogd pass messages to
the NT Event Log, as well.  Anyhow, the concept of running a full blown
installation of cygwin w/o any additional processes will be moot once
cygserver becomes mainstream.  IMHO, the NT Event Log is not very
extensible and, of course, is proprietary.  Just my 2 cents...

Cheers,
Nicholas

__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

--
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/

Re: Syslog (was: <no subject>)

[Corinna Vinschen]

On Mon, Jun 10, 2002 at 06:14:10AM -0700, Nicholas Wourms wrote:
> If you are going to emulate *n*x, you are going have to run some
> processes.  Memory is cheap, and certainly the syslogd wouldn't use that
> much, would it?  Also, it's not like you couldn't have the messages fall
> back to the NTeventlog or Ugly-syslog, should the service not be started
> or fail.  I bet it would even be possible to have syslogd pass messages to
> the NT Event Log, as well.  Anyhow, the concept of running a full blown
> installation of cygwin w/o any additional processes will be moot once
> cygserver becomes mainstream.  IMHO, the NT Event Log is not very
> extensible and, of course, is proprietary.  Just my 2 cents...

Memory is obviously not a problem but:

- The base tools needed to build programs (gcc/as/ld/etc) always
  will have to run w/o starting some service.

- Even if cygserver is becoming mainstream, Cygwin will still
  have to run nicely w/o cygserver.  No base functionality
  (e. g. fork()) may require cygserver.

- The openlog/syslog calls in the kernel should work even if
  no syslogd is running.  This will become somewhat tricky
  if each call has to check the existance of a running syslogd
  to be able to fallback to event log if it's not running (The
  connection is..., well, connectionless.  Syslog is using UDP).
  Ok, that's easy to solve...

The solution if we going to utilize syslogd has to fulfill
these requirements.  Basically Cygwin is still only an emulation
layer to allow building and running POSIX applications, not
a full substitute for an OS (even if we're not *that* far away ;-)).

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
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/

Re: Syslog (was: <no subject>)

[Christopher Faylor]

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/

Re: Syslog (was: <no subject>)

[Tony Arnold]

On Mon, 10 Jun 2002, Christopher Faylor wrote:

> >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.

Must be my memory playing tricks as I cannot find the message in the mail
archives. Did you ask a question about moving code to do with syslog and
syslogd from one place to another or something along those lines? It was
probably a year ago?

Regards,
Tony.
-- 
Tony Arnold, Deputy to the Head of COS Division, Manchester Computing,
University of Manchester, Oxford Road, Manchester M13 9PL.
T: +44 (0)161 275 6093, F: +44 (0)870 136 1004, M: +44 (0)773 330 0039
E-mail: tony.arnold@man.ac.uk, Home: http://www.man.ac.uk/Tony.Arnold


--
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/