ep: command n
ot found
/usr/share/csih/cygwin-service-installation-helper.sh: line 2472: awk: command n
ot found
/usr/share/csih/cygwin-service-installation-helper.sh: line 2473: awk: command n
ot found
*** Warning: The permissions on the directory /var are not correct.
*** Warning: They must match the
Hi,
I found that syslogd is not logging cron jobs after a computer restart:
These are working cron jobs that had been successfully logged
(before restart):
Mar 23 22:55:01 Penguin-PC /usr/sbin/cron: PID 7432: (Penguin) CMD ...
Mar 23 23:00:01 Penguin-PC /usr/sbin/cron: PID 5204
On Nov 16 08:07, Heiko Elger wrote:
> Hello,
>
> I'm sorry - but cause of sometimes having unpredictable and unreproduceable
> cygwin errors like "fork error, cygheap check", I trieded to run syslogd to
> log these all these errors in /var/log/messages.
>
&
Hello,
I'm sorry - but cause of sometimes having unpredictable and unreproduceable
cygwin errors like "fork error, cygheap check", I trieded to run syslogd to
log these all these errors in /var/log/messages.
But these kind of errors are not logged there.
How do I have to confi
Dave Korn wrote:
> On 28 August 2007 15:49, Will Parsons wrote:
>
>> I had a working syslogd on my computer at work, but now the computer has
>> been replaced (the IT department copied over the contents from the old
>> computer)
>
> Please god they didn'
On 28 August 2007 15:49, Will Parsons wrote:
> I had a working syslogd on my computer at work, but now the computer has
> been replaced (the IT department copied over the contents from the old
> computer)
Please god they didn't use the 'doze "Files and Settings transf
with!
Thanks again and best regards,
Doug Irwin
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of René Berber
> Sent: Sunday, 2 April 2006 14:37 PM
> To: cygwin@cygwin.com
> Subject: Re: 1.5.18-1: syslogd and cron message issue (X
René Berber wrote:
[snip]
> After compiling and installing the changed version I'm getting this ugly
> message:
>
> Apr 1 18:33:31 b kernel: cron[2812]: segfault at 004060C2 rip 00402986 rsp
> 0022E850 error 6
>
> But cron is working normally, so it may be just a non related problem
> (possibl
Irwin, Doug wrote:
> I have set up /etc/syslog.conf to exclude logging cron messages but
> still seem to be getting them.
>
> In syslogd I have tried the following:
> *.*;cron.none /var/log/messages
That one should be enough.
[snip]
> What is getting logged is soemthi
I have set up /etc/syslog.conf to exclude logging cron messages but
still seem to be getting them.
In syslogd I have tried the following:
*.*;cron.none /var/log/messages
*.info;cron.none /var/log/messages
*.*;cron.warn /var/log/messages
*.info;cron.warn
Pop.
Any thoughts? Anyone?
-doug
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Irwin, Doug
> Sent: Thursday, 23 March 2006 16:57 PM
> To: cygwin@cygwin.com
> Subject: Problem with syslogd and cron...
>
> Hi all,
&
Hi all,
I have the following...
In the crontab:
1-59 * * * * /echo_the_date.ksh >> /echo_the_date.log
In /echo_the_date.ksh:
#ksh
/bin/date
In /etc/syslog.conf:
*.*;cron.none /var/log/messages
My question is, why do I still get this logged into /var/log/messages?
Mar 23 16:52:00 DOUG /USR/S
> You must allow logging from remote hosts on the target machine. See the
> syslogd -s option. Remote logging from a Cygwin client syslogd to a
> Linux syslogd works fine here.
Thanks. It works indeed. It was an issue of a firewall...
__
Este mensaje, y e
On Oct 10 13:43, Jaime Saiz Santos wrote:
> >> Hi.
> >> Is it possible to log messages to a remote syslogd server?
> >> In theory it could be done by putting something like "*.*
> >> @hostname" in /etc/syslog.conf.
> >
> >Why
> Hi.
> Is it possible to log messages to a remote syslogd server?
> In theory it could be done by putting something like "*.*
> @hostname" in /etc/syslog.conf.
Why don't you just try?
Sorry.
I haven't said I have tried it before: it works for a l
On Oct 10 12:26, Jaime Saiz Santos wrote:
> Hi.
> Is it possible to log messages to a remote syslogd server?
> In theory it could be done by putting something like "*.*
> @hostname" in /etc/syslog.conf.
Why don't you just try?
Corinna
--
Corinna Vinschen
Hi.
Is it possible to log messages to a remote syslogd server?
In theory it could be done by putting something like "*.*
@hostname" in /etc/syslog.conf.
Thank you,
Jaime
__
Este mensaje, y en su caso, cualquier fichero anexo al mismo,
puede contener i
s a record of all login/logout activity. It's not related
to syslogd.
> Also, can you (generally) HUP a service and expect it
> to re-read a configuration file? (If it would do so
> on a kill -s HUP signal that is).
Generally, no. Windows services have no idea what a SIGHUP is
I added SysLogD as a service to my Cygwin server
(because I wanted to support SpamD logging to it
for SpamAssassin.)
CYGWIN syslogd is started and running as a service.
(And SpamD stopped emitting a warning about unable to
find syslogd when it starts.)
/var/log/sylogd.log was created at that
Christopher Faylor wrote:
> Wouldn't "ps -W" and "/bin/kill -f" work here, too?
Probably. Though ps doesn't tell you which cygrunsrv is which, if you
have more than one running and don't want to kill an innocent service,
which is why I use procexp. "procps aux --forest" works too.
Brian
--
Un
On Thu, Apr 21, 2005 at 02:21:39PM -0700, Brian Dessent wrote:
>"Thompson, Lloyd D. (SSD)" wrote:
>
>> $ net stop syslogd
>> The service could not be controlled in its present state.
>>
>> More help is available by typing NET HELPMSG 2189.
>>
>>
"Thompson, Lloyd D. (SSD)" wrote:
> $ net stop syslogd
> The service could not be controlled in its present state.
>
> More help is available by typing NET HELPMSG 2189.
>
> $ net helpmsg 2189
>
> The service could not be controlled in its present state.
I
Hello,
I'm trying to start the cygwin syslog daemon. I set it up using
syslogd-config, then try and start it with either "net start" or
"cygrunsrv -S". The service never fully starts. The return of both
commands states that the service could not be started.
It does
On May 11 00:05, C Wells wrote:
> I know you can set syslog.conf to point to a remote
> syslog daemon, so if you use logger it will get copied
> to the remote syslogd, however is there a command in
> cygwin (or linux for that matter) that you can use to
> send a syslog message direc
I know you can set syslog.conf to point to a remote
syslog daemon, so if you use logger it will get copied
to the remote syslogd, however is there a command in
cygwin (or linux for that matter) that you can use to
send a syslog message directly to a remote syslogd ?
logger seems to write to only
Hi!
I want to log remote messages from linux machines on my cygwin machine.
There
is a version of syslogd for cygwin available but the functionality to
receive remote
messages is missing.
Does anyone have an idea for a different approach to achieve this
functionality?
Mario
--
Unsubscribe
rce for this package,
then go into /usr/src/inetutils-*, run "configure", cd to syslogd, run
"make" and you will have a working syslogd.
Once you have done this, you should create a /etc/syslog.conf file. I have
syslogd running as a service with cygrusrv and with the arguments
Hi,
I'm curious to know if there is any way to write syslog messages to a
file instead of to the XP Event Viewer.
I actually installed Cygwin for *nix tools such as syslogd to use with
my Cisco equipment. I could not find a syslogd for Windows that I was
happy with, so I was hoping to ju
28 matches
Mail list logo
