On 2025-05-04 13:14, Sam Edge via Cygwin wrote:
On 28/03/2025 11:20, Sam Edge via Cygwin wrote:
On 28/03/2025 11:00, Sam Edge via Cygwin wrote:
I've had a weird regression with syslog-ng recently. Dunno if it's
related to a new release of the Cygwin DLL because I've only
On 2025-05-04 3:14 p.m., Sam Edge via Cygwin wrote:
Calling the maintainer for syslog-ng and/or libglib2.0. The latest
Cygwin release of these packages are still exhibiting the same assertion.
If syslog-ng has become orphaned could someone please let me know and
I'll check it out mysel
On 28/03/2025 11:20, Sam Edge via Cygwin wrote:
On 28/03/2025 11:00, Sam Edge via Cygwin wrote:
I've had a weird regression with syslog-ng recently. Dunno if it's
related to a new release of the Cygwin DLL because I've only just
spotted it.
When I try to start syslog-ng as a s
Hi all.
I've had a weird regression with syslog-ng recently. Dunno if it's
related to a new release of the Cygwin DLL because I've only just
spotted it.
When I try to start syslog-ng as a service recently it fails to load
with the following in /var/log/syslog-ng.log.
cat /var/lo
The following packages have been uploaded to the Cygwin distribution:
* syslog-ng-3.2.5-3
This is just a rebuild updating from OpenSSL 1.0 to OpenSSL 1.1.
Syslog-ng is a next generation system logger daemon which provides more
capabilities and has a more flexible configuration then the
On Aug 18 13:35, Matthew Hatch wrote:
> On 08/18/2016 03:39 AM, Corinna Vinschen wrote:
> > On Aug 17 16:09, Matthew Hatch wrote:
> >> Hi,
> >>
> >> I've noticed that syslog-ng hasn't received much attention in cygwin
> >> and is several
On 08/18/2016 03:39 AM, Corinna Vinschen wrote:
> On Aug 17 16:09, Matthew Hatch wrote:
>> Hi,
>>
>> I've noticed that syslog-ng hasn't received much attention in cygwin
>> and is several years out of date (3.2.5). As such, it is missing some
>> feature
On Aug 17 16:09, Matthew Hatch wrote:
> Hi,
>
> I've noticed that syslog-ng hasn't received much attention in cygwin
> and is several years out of date (3.2.5). As such, it is missing some
> features that are useful and pretty standard today in most syslog
> daemons
Hi,
I've noticed that syslog-ng hasn't received much attention in cygwin
and is several years out of date (3.2.5). As such, it is missing some
features that are useful and pretty standard today in most syslog
daemons (ie: support for multi-line messages). Is there any chance of
I have updated syslog-ng to 3.2.5-2.
Nothing new, just an update to link against the latest pcre DLLs.
Have fun,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
--
Problem reports
f you do it first, it MUST be first - before
you open any fds that must not be accidentally closed. sendmail is
indeed buggy for trying to use syslog() (which uses an fd) prior to
doing the orgy close.
>
> Could it be that incoming e-mail is such a volatile process that previous
> open
how many open fds
sendmail inherited from its parent process (once typically an rc shell
script) which was questionable back in the days sendmail was young I
guess, and if sendmail forks/execs, it's a way to disallow arbitrary fds
inheritance by the child.
> Could it be that incoming e-m
CS it's a bug in sendmail. Take a look
> into your newaliases.strace.txt file. Start at line 260 (stripping
> off timestamp, thread and process info):
>
> 260: normalize_posix_path: src /dev/log
>
> Here the syslog() function tries to open a connection to a syslog
ripping
off timestamp, thread and process info):
260: normalize_posix_path: src /dev/log
Here the syslog() function tries to open a connection to a syslogd
listening on /dev/log.
282: cygwin_socket: 3 = socket(1, 2 (flags 0x0), 0)
Socket created, file descriptor is 3.
296: connect_sysl
Corinna Vinschen wrote:
>
> Can you produce another strace for the overwriting case (non-R/O aliases)
> for comparison? Also, can you do the same strace with no syslogd running?
>
> It might be necessary to create a few test versions of Cygwin with more
> debug output, but let's please see these
t; > > bytes
> > > total
> > >
> > > If I make the 'aliases' file read-only, then the file is not corrupted,
> > > but the
> > > error occurs.
> >
> > I don't see that this has to do with syslog. There's a writev to
;m getting the 'Bad file descriptor' system error after building the mail
> > aliases
> > database. The building itself is done successful, but logging the event to
> > the
> > system log fails with this message.
>
> Did you mention whether you've insta
ng the 'Bad file descriptor' system error after building the mail
> >aliases
> >database. The building itself is done successful, but logging the event to
> >the
> >system log fails with this message.
>
> Did you mention whether you've installed an
oot
> www: root
> ftp: root
> abuse: root
> noc: root
> security: root
> root: SYSTEM
> <22>sendmail: PID 1848: /etc/mail/aliases: 9 aliases, longest 6 bytes, 82
> bytes
> total
>
> If I make the 'aliases' file read-only, then the file is not corrup
itself is done successful, but logging the event to the
system log fails with this message.
Did you mention whether you've installed and configured some syslog service?
--
Larry
_
A: Yes.
> Q: Are you sure?
>> A:
s
total
If I make the 'aliases' file read-only, then the file is not corrupted, but the
error occurs.
Cheers,
Daniel
Here's the strace output. I copied the lines between two subsequent calls to
'syslog':
strace /usr/sbin/sendmail -bi
syslog: Bad file descriptor
145 169
I have updated syslog-ng to the upstream release 3.2.5.
The upstream package needed a few minor patches, mainly a heartily
autoreconf, as well as adding a missing cygwin-specific file. The
package is now created using cygport.
To update your installation, click on the "Install Cygwin now&
Oh yes - you are right. And I had already seen it before I issued my record,
sorry. But when I started the description I thought I would get somewhere and
forgot about your experience. It is the same problem; after deleting
syslog-ng.persist I could start the service. Thank you.
Ulrich
Ken Brown
On 3/27/2012 12:16 PM, Corinna Vinschen wrote:
On Mar 27 11:40, Ken Brown wrote:
On 3/27/2012 7:47 AM, Ulrich Schmidt wrote:
$ cygrunsrv -S syslog-ng
cygrunsrv: Error starting a service: QueryServiceStatus: Win32 error 1062:
The service was not started.
This might be a known problem with
On Mar 27 11:40, Ken Brown wrote:
> On 3/27/2012 7:47 AM, Ulrich Schmidt wrote:
> >$ cygrunsrv -S syslog-ng
> >cygrunsrv: Error starting a service: QueryServiceStatus: Win32 error 1062:
> >The service was not started.
>
> This might be a known problem with syslog-ng.
On 3/27/2012 7:47 AM, Ulrich Schmidt wrote:
$ cygrunsrv -S syslog-ng
cygrunsrv: Error starting a service: QueryServiceStatus: Win32 error 1062:
The service was not started.
This might be a known problem with syslog-ng. See the thread starting at
http://cygwin.com/ml/cygwin/2011-10
E-Mail lesen « 1 Von 22 »
Environment:
Windows 7/32
Cygwin 1.7.11-1
OpenSSH 5.9p1-1
syslog-ng 3.2.1-1
Dear Community,
Im just started with Cygwin and want to run openSSH. Im getting slowly furher
On Oct 22 18:04, Ken Brown wrote:
> I have syslog-ng running on two 64-bit Win7 systems, and the service
> stops periodically and can't be restarted. The file
> /var/log/syslog.ng log contains many lines saying
>
> Persistent configuration file is in invalid format
On 10/22/2011 6:04 PM, Ken Brown wrote:
I have syslog-ng running on two 64-bit Win7 systems, and the service
stops periodically and can't be restarted. The file /var/log/syslog.ng
log contains many lines saying
Sorry, the file is /var/log/syslog-ng.log .
Persistent configuration file
I have syslog-ng running on two 64-bit Win7 systems, and the service
stops periodically and can't be restarted. The file /var/log/syslog.ng
log contains many lines saying
Persistent configuration file is in invalid format, ignoring;
But apparently it doesn't ignore the error, and
I have updated syslog-ng to the latest stable release 3.2.1.
The upstream package needed a few minor patches.
The package now comes with a postinstall script and an enhanced
/bin/syslog-ng-config file in order to allow to change the syslog-ng file
layout to be more aligned to the typical Linux
On Jan 18 22:55, Paul McFerrin wrote:
> I discovered that cygwin has both packages for "eventlog" and "syslog-ng.
>
> I searched for cygwin documentation in "man", "info", and the
> command itself. I have them both installed, (says setup.exe) but I
Subject should read: Can't find any info on "eventlog" and "syslog-ng"
Paul McFerrin wrote:
I discovered that cygwin has both packages for "eventlog" and "syslog-ng.
I searched
I discovered that cygwin has both packages for "eventlog" and "syslog-ng.
I searched for cygwin documentation in "man", "info", and the command
itself. I have them both installed, (says setup.exe) but I can only
find the command itself for "syslog-ng
amily = AF_LOCAL;
> > strcpy(sa.sun_path, "/dev/log");
> > connect(sd, (struct sockaddr *)&sa, sizeof(sa));
> >
> > struct iovec iv[2] = { { "<1>", 3 }, { "test: text", 10 } };
> > writev(sd, iv, 2);
>
> Yes, but... why is th
d, { {"< PRI >", . }, { "MSG", . } }, 2)
> > > > used within syslog() sends "< PRI >" and "MSG" in
> > > > two separate datagrams to /dev/log.
> > > >
> > >
> > > Probably not. The "
On Dec 2 12:07, Christian Franke wrote:
> Corinna Vinschen wrote:
> > On Dec 2 10:31, Christian Franke wrote:
> > > I presume that the root of the problem is that the
> > >
> > > writev(fd, { {"< PRI >", . }, { "MSG", . } }, 2)
>
Corinna Vinschen wrote:
> On Dec 2 10:31, Christian Franke wrote:
> > I presume that the root of the problem is that the
> >
> > writev(fd, { {"< PRI >", . }, { "MSG", . } }, 2)
> > used within syslog() sends "< PRI >" and &q
On Dec 2 10:31, Christian Franke wrote:
> syslog() produces bogus lines in /var/log/messages.
>
> Testcase (with syslog-ng):
>
> $ echo -e 'one\ntwo\nthree' | logger -t test
>
> $ tail /var/log/messages
> ...
> Dec 2 10:12:31 localhost kernel:
> Dec 2
syslog() produces bogus lines in /var/log/messages.
Testcase (with syslog-ng):
$ echo -e 'one\ntwo\nthree' | logger -t test
$ tail /var/log/messages
...
Dec 2 10:12:31 localhost kernel:
Dec 2 10:12:31 localhost test: one
Dec 2 10:12:31 localhost kernel:
Dec 2 10:12:31 localhost
On Sep 28 16:46, Julio Costa wrote:
> Hi,
>
> On Thu, Mar 19, 2009 at 17:36, Julio Emanuel <> wrote:
> > Hi Corinna (I think this is with you),
> >
> > I've been struggling with a small (but deadly) problem in the current
> > syslog-ng package:
>
Hi,
On Thu, Mar 19, 2009 at 17:36, Julio Emanuel <> wrote:
> Hi Corinna (I think this is with you),
>
> I've been struggling with a small (but deadly) problem in the current
> syslog-ng package:
> ~ $ cygcheck -c syslog-ng
> Cygwin Package Information
> Package
On Mar 20 14:39, Julio Emanuel wrote:
> Answering to myself: after some source code analysis, I've arrived to
> this tiny function in misc.c:
>
> gboolean
> resolve_user(const char *user, uid_t *uid)
> {
> struct passwd *pw;
>
> *uid = 0;
> if (*user)
> return FALSE;
>
> pw = getpwna
On Thu, Mar 19, 2009 at 23:49, Julio Emanuel wrote:
> On Thu, Mar 19, 2009 at 18:29, Corinna Vinschen wrote:
>>
>>> Now, for the part I didn't manage to solve yet: the syslog-ng service
>>> also spits this warning (error?) when starting: "Error resolving use
you're a
> package maintainer or you're providing code to setup.exe. Thanks.
>
Ooops. Sorry for the noise.
And the funny thing is, I told myself two or three times to not forget
to check the correct list. Things happen! :)
>>
>> ...to put the 'lost colon' back in
I have updated syslog-ng for Cygwin 1.7 to the latest stable release
3.0.1. The 3.x series is a major new upstream release which contains a
lot of improvements and bug fixes over the 2.x series.
To update your installation, click on the "Install Cygwin now" link on
the http://cygwi
On Jan 14 11:06, Joost De Cock wrote:
> Hello there,
>
> I noticed that syslog-ng 3.0.1 has been released
> <https://lists.balabit.hu/pipermail/syslog-ng/2009-January/012370.html> on
> Jan 12, 2009 and it looks very yummi to me.
>
> Now, the current syslog-ng ve
Hello there,
I noticed that syslog-ng 3.0.1 has been released
<https://lists.balabit.hu/pipermail/syslog-ng/2009-January/012370.html>
on Jan 12, 2009 and it looks very yummi to me.
Now, the current syslog-ng version in Cygwin (2.0.7) was released on Jan
8, 2008
<https://lists.b
I have updated syslog-ng on cygwin.com to the latest stable release
2.1.1. The Cygwin version is built from the vanilla sources.
There's a -1 release for Cygwin 1.5.25 and, for 1.7 testing folks,
a IPv6-enabled -2 release.
Please read /usr/share/doc/Cygwin/syslog-ng.README for postin
On Fri, Aug 22, 2008 at 11:19:34AM -0400, Larry Hall (Cygwin) wrote:
> On 08/22/2008, Grav Yam wrote:
>>In fact, I actually thought about emailing you or Corinna directly
>>about this, but I didn't know if that was proper list etiquette.
>
>Sending email to the list is the recommended method of com
On 08/22/2008, Grav Yam wrote:
In fact, I actually thought about emailing you or Corinna directly about
this, but I didn't know if that was proper list etiquette.
Sending email to the list is the recommended method of communication so
you made the right call.
--
Larry Hall
> You didn't look at this list archive, where I reported this problem long
> ago, and to the syslog-ng list, where somebody reported it on Linux,
> also long ago. By long ago I mean 3 or 4 versions back, but the problem
> is still there.
Woah - simmer down cowboy.
To be fair R
Grav Yam wrote:
> Even when nothing else is happening, and nothing is being logged, the
> syslog-ng service is consistently using up 50% of my cpu under a
> win2k host.
>
> I've looked though the mailing list archives and also googled around
> a lot looking for a solution
Hi -
Even when nothing else is happening, and nothing is being logged, the syslog-ng
service is consistently using up 50% of my cpu under a win2k host.
I've looked though the mailing list archives and also googled around a lot
looking for a solution, but no one else seems to really have
I have updated syslog-ng on cygwin.com to the latest stable release
2.0.7. The Cygwin version is called 2.0.7.1. It's taken from the
current state of the syslog-ng upstream git repository, which contains
Cygwin related patches beyond the official 2.0.7 release.
Please read /usr/share/doc/C
Dave Korn artimi.com> writes:
>
> On 13 November 2007 10:25, Tony Benham wrote:
>
> > I ran mkpasswd -d domain >> /etc/passwd to recreate passwd. But the problem
> > remains. I cannot see the SYSTEM user in the file. Is there a switch for
> > mkpasswd I need to use ?
>
> Try -l *as well*.
On 13 November 2007 10:25, Tony Benham wrote:
> I ran mkpasswd -d domain >> /etc/passwd to recreate passwd. But the problem
> remains. I cannot see the SYSTEM user in the file. Is there a switch for
> mkpasswd I need to use ?
Try -l *as well*. Then no need to append:
mkpasswd -l -d > /etc/p
Corinna Vinschen cygwin.com> writes:
>
> On Nov 12 18:22, Tony Benham wrote:
> > I've decided to run syslog-ng on my cygwin installation. I updated to latest
> > version 2.0.5.1. When I run syslog-ng-config I get four errors
> > setfacl : illegal acl entries
On Nov 12 18:22, Tony Benham wrote:
> I've decided to run syslog-ng on my cygwin installation. I updated to latest
> version 2.0.5.1. When I run syslog-ng-config I get four errors
> setfacl : illegal acl entries
>
> Is this to be expected ?
All four setfacl calls try to ad
I've decided to run syslog-ng on my cygwin installation. I updated to latest
version 2.0.5.1. When I run syslog-ng-config I get four errors
setfacl : illegal acl entries
Is this to be expected ?
I then modified syslog-ng.conf to change root group to Administrators as I don't
have a
I have updated syslog-ng on cygwin.com to the latest stable release
2.0.5. The 2.x series is a major new upstream release which contains a
lot of improvements and bug fixes over the 1.6.x series.
The binary is now much bigger because syslog-ng is by default linked
statically to the support
On Apr 26 13:28, S. Schulz wrote:
> I found a bug in syslog-ng-1.6.12.
> If i use the MSGONLY macro the first char of the message is missing.
>
> Here is the patch:
> -snip
> 426,427c426,428
> < colon++;
> < of
I found a bug in syslog-ng-1.6.12.
If i use the MSGONLY macro the first char of the message is missing.
Here is the patch:
-snip
426,427c426,428
< colon++;
< ofs = (colon - (char *) msg->msg->data);
---
> ofs =
I have updated syslog-ng on cygwin.com to the latest stable release
1.6.12. This is just a minor update which contains scalability
improvements and bug fixes.
syslog-ng, as the name shows, is a syslogd replacement, but with new
functionality for the new generation. The original syslogd allows
René Berber wrote:
> Corinna Vinschen wrote:
> [snip]
>> I'm using syslog-ng all the time and I never had this problem. I'm
>> wondering if you just have a dependency problem since that seems to
>> happen on some systems but not on others. What happens if you a
Corinna Vinschen wrote:
[snip]
> I'm using syslog-ng all the time and I never had this problem. I'm
> wondering if you just have a dependency problem since that seems to
> happen on some systems but not on others. What happens if you add
> a dependency to tcpip to the sy
currently I'm using
> 1.5.21 and this is under Windows XP-Pro sp2.
>
> Syslog-ng was installed as a service following the instructions in the README
> and it works fine (even when it's looping), some info:
>
> $ cygrunsrv -Q syslog-ng
> Service : syslo
I have updated syslog-ng on cygwin.com to the latest stable release
1.6.11. This is just a minor update which contains scalability
improvements and a change to the documentation.
syslog-ng, as the name shows, is a syslogd replacement, but with new
functionality for the new generation. The
g the -x option to cygrunsrv, pointing it to the syslog-ng
> pid file (that you specify via the -p option to syslog-ng), and then *not*
> specifying the -F option to syslog-ng.
I had not considered to combine the options! Yes, this worked:
$ cygrunsrv -R syslog-ng
$ cygrunsrv -I syslog-ng -d &quo
On Mon, 3 Apr 2006, Bryan D. Thomas wrote:
> > To generate a pidfile for syslog-ng, should I try the
> > -p switch to syslog-ng, (i.e. using the -a argument to
> > cygrunsrv) or the -x argument to cygrunsrv?
>
> I tried removing the service using cygrunsrv, then installin
> To generate a pidfile for syslog-ng, should I try the
> -p switch to syslog-ng, (i.e. using the -a argument to
> cygrunsrv) or the -x argument to cygrunsrv?
I tried removing the service using cygrunsrv, then installing the service
with the changed option. But, when starting the serv
My syslog-ng on Cygwin does not have an associated
/var/run/syslog-ng.pid file. I'd like to have this as
an aid to rotating the logs.
To generate a pidfile for syslog-ng, should I try the
-p switch to syslog-ng, (i.e. using the -a argument to
cygrunsrv) or the -x argument to cygrunsrv? Or,
"René Berber" <[EMAIL PROTECTED]> wrote:
> The problem I guess is that you have more than one sshd process running,
> are
> the syslog messages the same as the ones in the event log?
"Corinna Vinschen" <[EMAIL PROTECTED]> wrote:
> If you add a depe
On Mar 21 13:45, Bryan D. Thomas wrote:
> I've found in cygrunsrv.README that the -1 and -2
> arguments may be used to specify that output of stdout
> and stderr go to a log file instead of to the Windows
> Event Log.
>
> I'm using cygrunsrv to run two services: sshd
that.
The problem I guess is that you have more than one sshd process running, are the
syslog messages the same as the ones in the event log?
If you don't have several sshd processes then you did something while installing
the service that caused the problem. Stop and remove the service (o
ices are
> started
> at the same time (automatic in services starup type).
What you say is correct. I am getting log lines in my sshd.log with
timestamps, and my filters in syslog-ng.conf are working. However, I am
also still getting lines from sshd in my Application Event Log.
My goal is
ch is to
send any cygrunsrv output to /var/log/ which usually is empty
since each service does its own logging.
> I'm using cygrunsrv to run two services: sshd and
> syslog-ng. I'm using syslog-ng to collect timestamped
> log entries from sshd and do postprocessing with
> filters.
I've found in cygrunsrv.README that the -1 and -2
arguments may be used to specify that output of stdout
and stderr go to a log file instead of to the Windows
Event Log.
I'm using cygrunsrv to run two services: sshd and
syslog-ng. I'm using syslog-ng to collect timestamped
log en
I have uploaded syslog-ng-1.6.9-1.
syslog-ng, as the name shows, is a syslogd replacement, but with new
functionality for the new generation. The original syslogd allows
messages only to be sorted based on priority/facility pairs; syslog-ng
adds the possibility to filter based on message contents
On Dec 31 22:38, Hiroki Sakagami wrote:
> When I use LOG_PERROR option on openlog() call, syslog() does not
> append a newline to the log message. Is this an intentional behavior?
It's a bug. I've fixed it in CVS.
Thanks for the report,
Corinna
--
Corinna Vinschen
Hi,
When I use LOG_PERROR option on openlog() call, syslog() does not
append a newline to the log message. Is this an intentional behavior?
--
Hiroki Sakagami
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Igor Pechtchanski wrote:
> Why complicate openlog()? Let the Cygwin applications that use openlog()
> do this (e.g., in a postinstall script). We could even add a utility
> package in "Base", similar to "editrights", that contains scripts for
> adding and removing this setting (something like 'r
On Thu, 24 Nov 2005, Brian Dessent wrote:
> Christian Franke wrote:
>
> > Unlike syslog, windows event log is intended to store only message
> > parameters, not complete messages.
> > The (probably localized) messages must be provided by such an "event
> > me
On Aug 25 23:34, Samuel Thibault wrote:
> Hi,
>
> This crashes (yes it's odd code, but it shouldn't crash):
>
> #include
> #include
>
> int main(void) {
> errno = -1;
> syslog(LOG_ERR,"foo");
> }
>
> Indeed, one of the
Hi,
This crashes (yes it's odd code, but it shouldn't crash):
#include
#include
int main(void) {
errno = -1;
syslog(LOG_ERR,"foo");
}
Indeed, one of the first things that vsyslog does is
char *errtext = strerror (get_errno ());
int errl
On Jun 30 16:47, Tony Karakashian wrote:
> Following your advice, I installed the default syslog as a
> Windows service, and /dev/log is created, but only when syslog is
> running. How do I create it so it's always available?
You don't. /dev/log is supposed to be a AF_U
> Dunno what you're up to but I'm running syslog from inetutils just
> fine. Cygwin tries to syslog on /dev/log if it's available (it's
> usually created by syslog) and there's also a /dev/kmsg pipe which
> would be utilized for kernel messages ... *if* Cyg
On Jun 30 15:19, Tony Karakashian wrote:
> I've seen lots of people who got syslog-ng working on their cygwin
> boxes. Latest version compiles just fine out of the box, but not sure
> what I should put in for a source in the syslog-ng.conf? Default for
> Linux is to use /proc/km
I've seen lots of people who got syslog-ng working on their cygwin
boxes. Latest version compiles just fine out of the box, but not sure
what I should put in for a source in the syslog-ng.conf? Default for
Linux is to use /proc/kmesg, but we don't have one under Cygwin. Are
Cygwi
On Mon, Sep 29, 2003 at 07:03:42AM -0500, Scott Bolte wrote:
>could you add a
> check of return code from ReportEventA()? That might shed
> light on the problem.
I've added a debug message. Should be in the next developers snapshot.
Corinna
--
Corinna Vinschen
>
> > It seems like cygwin syslog on w2k, both the logger command the
> > syslog(3) routine, works only for the SYSTEM account. Is that true?
>
> No. Perhaps the users privileges don't allow that? Members of the
> group "Users" (or the native analogon
On Sun, Sep 28, 2003 at 03:16:54PM -0500, Scott Bolte wrote:
> It seems like cygwin syslog on w2k, both the logger command the
> syslog(3) routine, works only for the SYSTEM account. Is that true?
No. Perhaps the users privileges don't allow that? Members of the
group "Users
It seems like cygwin syslog on w2k, both the logger command the
syslog(3) routine, works only for the SYSTEM account. Is that true?
I have a test script that uses logger. When I call it manually no messages
appear in the event log. When I turn it into a service, where it is invoked
with SYSTEM
On Fri, Sep 12, 2003 at 04:40:27PM +1000, David O'Shea wrote:
>Hi all,
>
>>From reading the archives there seem to be some requests from people
>to have the ability to use a syslog daemon instead of the Windows
>Event Log or C:\CYGWIN_SYSLOG.TXT for syslog output. I woul
Hi all,
>From reading the archives there seem to be some requests from people
to have the ability to use a syslog daemon instead of the Windows
Event Log or C:\CYGWIN_SYSLOG.TXT for syslog output. I would also
like that.
I would like to try to implement this so that a registry flag contr
On Sat, 22 Feb 2003, Pierre A. Humblet wrote:
> On Win98 sshd fills syslog with error lines such as
>
> 2003-02-22 18:33:26 : sshd : PID 213289 : LOG_ERR :
> error: Failed to disconnect from controlling tty.
> 2003-02-22 18:33:32 : sshd : PID 771213 : LOG_INFO :
> syslo
On Win98 sshd fills syslog with error lines such as
2003-02-22 18:33:26 : sshd : PID 213289 : LOG_ERR :
error: Failed to disconnect from controlling tty.
2003-02-22 18:33:32 : sshd : PID 771213 : LOG_INFO :
syslogin_perform_logout: logout() returned an error
*
The first seems to
Hi all:
Thanks go to whoever fixed the bug in cygwin1.dll that caused syslog
to fail as soon as a udp packet was sent to it. The bug was introduced
sometime around 1.3.12, but is fixed now. So here is my recipe for
building syslog-ng-1.5.24.
Download syslog-ng-1.5.24 and libol-0.3.6. Patch the
On Wed, Dec 18, 2002 at 07:38:54PM -0500, Mikhail Teterin wrote:
>Although removing the syslogd seems natural, since the syslog(3) send
>the info directly to EventLog, it is wrong.
We didn't "remove" syslogd. It never existed.
Requests sent to the ether for someone to
Although removing the syslogd seems natural, since the syslog(3) send
the info directly to EventLog, it is wrong.
The syslog(3) should try to send to the local syslogd (at least, once
per program's life-time). Failing that, it can send to EventLog -- as it
currently does.
Then, the decisio
1 - 100 of 102 matches
Mail list logo
