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 Date: Tue, 2 Mar 2004 11:15:57 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Pb with permissions on crontab Message-ID: <20040302101557.GD21589@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <87znb4h525 DOT fsf AT jgilles DOT internal DOT glmultimedia DOT com> <87ishnljw7 DOT fsf AT jgilles DOT internal DOT glmultimedia DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87ishnljw7.fsf@jgilles.internal.glmultimedia.com> User-Agent: Mutt/1.4.2i On Mar 2 09:42, Julien Gilles wrote: > Julien Gilles writes: > > I'am playing with cron, and I have the following problem : I want to > > modify the crontab through a service (a cgi in an apache server in > > fact). This service belongs to the user SYSTEM, so I used "crontab -u > > Administrator file" to set the Administrator's crontab (in a perl cgi > > script). > > As I get no answer to my email, I suppose that I perhaps choose the > wrong mailing list. Should I contact directly the cygwin maintainer of No. The right place is here. Did you read the comment right before the chown command? Your patch is rather intrusive. It looks as if it will work only for privileged accounts now. Since you're using crontab from a shell script anyway, I don't see why you couldn't use chown or setfacl in the same script after calling crontab. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/