X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=I3
	z/q/dMISUF8jDlEtmKNsT3aStvE07F7nDvAcR4ve/HeLz4Hd6oNVbdWRA6Tun6ke
	JV0ARnFADmHaooZpwfqn0L1OJUBRz3k6ieC0EJ0HTVFwghYkEH4GKdVrkAMFlg/c
	u1hND26SWeSH1nih3dsNl1suE+0KXRV/6ns8CQxZg=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=Sj63bZgL
	+v43+0ry2WEeHJz8/BU=; b=r9y8a4DjnN60fW0plc9PGFtORkwkhTT/8xxlthFw
	8OAl9mdoWYg2V7VFJMXlSDnWm2My4maKrIMOSrIPeOx0GGEyoqkNVGh4li6c/0pD
	DHYda2L7jM/8vWXjgvg75xx+se+kDvmKg8vk0igU87l9SqTfMeBrFOqTo+1uVYni
	Fxk=
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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=2.9 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RDNS_NONE,SPF_PASS autolearn=no version=3.3.2
X-HELO:	mail-oa0-f66.google.com
MIME-Version:	1.0
X-Received:	by 10.60.70.134 with SMTP id m6mr28538421oeu.14.1385458056168; Tue, 26 Nov 2013 01:27:36 -0800 (PST)
In-Reply-To:	<CAMwOpcry6fkHwZC8thRjMuV=iZL3keP3SCrsjCroqWrEcQNa-w@mail.gmail.com>
References:	<CAMwOpcry6fkHwZC8thRjMuV=iZL3keP3SCrsjCroqWrEcQNa-w AT mail DOT gmail DOT com>
Date:	Tue, 26 Nov 2013 11:27:36 +0200
Message-ID:	<CAMwOpcp4heAtgg7fnMXdSw02iKO+Z5pwnBDC2GV6_zcLdjt_ag@mail.gmail.com>
Subject:	Re: Cygwin 1.5.25 issue: Crontab on Windows
From:	Aleksander Panayotov <aleksander DOT panayotov AT gmail DOT com>
To:	cygwin AT sourceware DOT org

It was actually a typo - a missing "2". What I meant was that I tested
it with the 1.7.25 version (the latest one that was on your website
last week) and not with 1.7.5.

On 25 November 2013 10:57, Aleksander Panayotov
<aleksander DOT panayotov AT gmail DOT com> wrote:
> Hello,
>
>
> I am writing to you in order to report a strange issue I encountered
> while using Cygwin 1.5.25 on Windows 2k8 R2 both SE SP1 & EE SP1.
>
> Introduction
>
> Cygwin installation is embedded in the installation of another
> product. Because of that, it is run with the same credentials as the
> installation the Cygwin is embedded in. I am using a rather simplified
> cygwin package containing the most basic functions.
>
> Main content
>
> The crontab utility, provided by Cygwin, is used to run maintenace
> scripts. Since everything is done during the installation, I
> encountered the following issue:
>
> 1) The installation of the product is initialized by the user X
>
> 2) During installation on the product, Cygwin installation is also
> initialized by the user X
>
> 3) The user X is not allowed to use the -u option when installing the
> cron service // cygrunsrv -I -u X - results in a deadlock, probably
> because of the lack of permissions of the user X.
>
> 4) After finishing the installation of both cygwin & cron, some
> cronjobs are added.
>
> 5) Having the cron service installed with the default user (SYSTEM),
> makes it impossible to add the cronjobs to the user X' crontab.
>
> 6) When checking user X' crontab, the jobs added are shown, but even
> if some of the entries are removed, the jobs continue to run (probably
> because they are added using the SYSTEM user).
>
> Summary
>
> The cron service is installed with the default user (SYSTEM) since
> there are no permissions to use -u. Jobs are also added with the user
> SYSTEM. The user X cannot edit SYSTEM's cron entries and those
> override everything else.
>
> Conclusion
>
> I would like to know if there is a way to work this around and if not,
> what should I do in order to have proper deployment of the
> cronjobs/cron service. I have also tested this on Cygwin 1.7.5 and I
> observe the same behaviour.
>
>
> Best regards,
>
> A. Panayotov

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

- Raw text -