X-Recipient: archive-cygwin@delorie.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:date:message-id:subject:from:to
	:content-type; q=dns; s=default; b=oFpzrO1YxvqbZ6f8NNObgvPRBtb8x
	L3QP3UxRB7/NJ0vClmqb9e9hMjwb+pS2aeoxv/674d/cFQ3qlsTkg2QCC4KtUgTS
	6uaZWQaACy/Yf/Q+K2I5JnAr2u4tirknyrQLAfcibUcjJZ4/c6crPxbcJQR86A2J
	12CAdMYaERSA3Y=
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:date:message-id:subject:from:to
	:content-type; s=default; bh=iEJwQ3rEn0nBCWb2tP4LLyIZ7Qo=; b=TFM
	4GDtzdAI6yz7i/S+4cV7IIn6lNUYgpW884NGAqppk6WWc9mvHmPAdSdXdsHnZIyw
	ubcotal98bX+ooh9wDix+07n7jcvLueP/h5SEDXTOEvEiTVqn6E0FohI5BYA/vQN
	WhHFVg2Xs1Bbs34k8eCgo08hzjmpMiqNzorZ5R28=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=4.2 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RDNS_NONE,SPF_PASS autolearn=no version=3.3.2
X-HELO: mail-ob0-f196.google.com
MIME-Version: 1.0
X-Received: by 10.60.62.132 with SMTP id y4mr376660oer.55.1385369854911; Mon, 25 Nov 2013 00:57:34 -0800 (PST)
Date: Mon, 25 Nov 2013 10:57:34 +0200
Message-ID: <CAMwOpcry6fkHwZC8thRjMuV=iZL3keP3SCrsjCroqWrEcQNa-w@mail.gmail.com>
Subject: Cygwin 1.5.25 issue: Crontab on Windows
From: Aleksander Panayotov <aleksander.panayotov@gmail.com>
To: cygwin@sourceware.org
Content-Type: text/plain; charset=ISO-8859-1

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

