Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: Problem running cygrunsrv with non SYSTEM accounts Date: Fri, 14 Jan 2005 14:38:32 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: <41E78CC6.4040104@familiehaase.de> Message-ID: X-OriginalArrivalTime: 14 Jan 2005 14:38:32.0156 (UTC) FILETIME=[B865F1C0:01C4FA46] > -----Original Message----- > From: cygwin-owner On Behalf Of Gerrit P. Haase > Sent: 14 January 2005 09:12 > To: Aitken, Sean > Aitken, Sean wrote: > > I have tried about anything. Does anyone know of any Win2K3 settings > > that would disallow certain acccounts from being worthy > service runners? > > There is a policy that disallows all code running in kernel > mode instead > of user mode, is sshd running in kernel mode? If so it is a > good thing > that it isn't allowed to run. Gerrit, you can't possibly mean what you're saying there. Kernel mode and User mode code are entirely different; it's nonsensical to suggest that one program could run in either mode. Do you perhaps mean "run as SYSTEM user / run as non-SYSTEM user"? Anyway, if running as SYSTEM it writes to /var/log/sshd.log, but running as an ordinary user it fails, then it's almost certainly the case that sshd.log is owned by SYSTEM user because it was first created by SYSTEM user. If that's the case "chmod a+rwx /var/log/sshd.log" should help. Also, nobody's told Sean to take a look in the windows event log yet, and see if there was any sign of life there. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/