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 Message-ID: <3E971B40.4432A9F1@ieee.org> Date: Fri, 11 Apr 2003 15:45:04 -0400 From: "Pierre A. Humblet" X-Accept-Language: en,pdf MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cron + network share(w/ full access?) References: <20030411014720 DOT GA4240 AT TGUN> <20030411015650 DOT GA35059733 AT hpn5170x> <20030411180224 DOT GA1712 AT TGUN> <3E970DAB DOT CB1DDEDE AT ieee DOT org> <20030411190340 DOT GB11137 AT cygbert DOT vinschen DOT de> <20030411171451 DOT GB635217 AT Worldnet> <20030411193313 DOT GD11137 AT cygbert DOT vinschen DOT de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Corinna Vinschen wrote: > > Well, it's the way cron works. Started from a privileged account > and then it changes user context to the owner of the crontab files > to start the applications. And for cron it is known (and documented > in /usr/doc/Cygwin/cron.README) that it should be started under SYSTEM. Right, what you did is very natural. However I am not sure that the initial setuid(18) in main.c is helpful at all on Cygwin. Removing it (as you already did in crontab.c) would allow: 1) Straight operation on Win9X 2) Running as a non-privileged user (for a single user) as the originator of this thread wanted to do, to access shared drive. > What's that problem with mkpasswd? The system account is created already > since October 2001. Yes on NT, but never on Win9X. > Anyway, I can change cron if it makes people happy... Thanks Corinna. From recent threads it looks like that would make people happy :) Pierre -- 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/