X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Will Parsons <wbp AT nodomain DOT invalid>
Subject:  Re: trouble starting syslogd
Date: Wed, 29 Aug 2007 16:57:17 +0000 (UTC)
Lines: 47
Message-ID:  <slrnfdb9bd.ifg.wbp@rowan.windsor>
References:  <fb1ckq$q3k$1 AT sea DOT gmane DOT org> <000601c7ea43$f281a6c0$2e08a8c0 AT CAM DOT ARTIMI DOT COM>
Reply-To: william DOT b DOT parsons AT us DOT westinghouse DOT com
User-Agent: slrn/0.9.8.1 (FreeBSD)
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

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't use the 'doze "Files and Settings transfer wizard".
> That totally messed up all my symlinks when I used it once.
>
>> Configuration finished. Have fun!
>> 151$ ls -l /etc/syslog.conf
>> -rwx------+ 1 wbp Domain Users 472 May 15 10:42 /etc/syslog.conf
>> 152$ chmod +r /etc/syslog.conf
>> 153$ chmod -x /etc/syslog.conf
>> 154$ ls -l /etc/syslog.conf
>> -rw-r--r--+ 1 wbp Domain Users 472 May 15 10:42 /etc/syslog.conf
>> 155$ cygrunsrv -L
>> syslogd
>> 156$ cygrunsrv -S syslogd
>> cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error 1062:
>> The service has not been started.
>
>   You need to take a look in the windows event log and see if you can find a
> more detailed error message there.

I did that, but it doesn't help me:

The description for Event ID ( 0 ) in Source ( syslogd ) cannot be
found. The local computer may not have the necessary registry information
or message DLL files to display messages from a remote computer. You may be
able to use the /AUXSOURCE= flag to retrieve this description; see Help and
Support for details. The following information is part of the event:
syslogd: PID 2720: `syslogd' service stopped, exit status: 0.

>> I've chmod'ed the files in /var/log so as to be readable and writable by
>> all.
>
>   Yeh, can't see anything immediately obviously wrong yet.  Maybe you could
> rerun the config, but this time answer 'yes' when it asks if it should
> overwrite the .conf file - save a copy of your current one, by all means, but
> it's a worthwhile experiment to try and narrow down the source of the trouble.

I renamed syslog.conf and re-ran syslogd-config to re-generate it, but with
the same effect, so I don't think I'm any further along.

- Will


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/