X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: =?UTF-8?B?UmVuw6kgQmVyYmVy?= Subject: Re: cron Date: Thu, 13 Sep 2007 01:00:00 -0500 Lines: 37 Message-ID: References: <1A1419D7B7E216498FA47FE7485F2354030A0F20 AT HQEXCLS01 DOT pbmr DOT co DOT za> <46E7FE86 DOT 2090902 AT cygwin DOT com> <01bf01c7f5c6$6164e380$46c11518 AT wirelessworld DOT airvananet DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) In-Reply-To: <01bf01c7f5c6$6164e380$46c11518@wirelessworld.airvananet.com> OpenPGP: url=hkp://wwwkeys.pgp.net X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Pierre A. Humblet wrote: [snip] > | On W2K3, if you expect a service to be able to switch user contexts, you > | need a special service account. You can use the 'sshd_server' account = that > | would be created for you if you configure 'sshd' and ask it to create t= he > | account when it asks you. See the "/usr/share/doc/Cygwin/openssh.READM= E" > | for details. >=20 > The above is correct, but later cron was switch to run as PolsonA Wrong, the log just shows that the user edited his crontab (i.e. did a `cro= ntab -e`) which does a reload on exit. Larry's diagnostic is right, cron should= n't be running as the user PolsonA. > 2007/09/12 16:19:31 [PolsonA] cron: PID 1432: `cron' service started > 2007/09/12 16:19:41 [PolsonA] crontab: PID 2844: (PolsonA) BEGIN EDIT (Po= lsonA) > 2007/09/12 16:19:46 [PolsonA] crontab: PID 2844: (PolsonA) REPLACE (Polso= nA) > 2007/09/12 16:19:46 [PolsonA] crontab: PID 2844: (PolsonA) END EDIT (Pols= onA) > 2007/09/12 16:20:01 [PolsonA] /usr/sbin/cron: PID 2564: (PolsonA) RELOAD = (tabs/PolsonA) > and everything looks normal (cron reloaded the crontab). > Did you wait long enough for the jobs to run? > Please look at cron.log in the home directory of PolsonA, and possibly a= t /tmp/*cron* files for=20 > further output from the jobs. --=20 Ren=C3=A9 Berber -- 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/