This is the mail archive of the
mailing list for the Cygwin project.
Re: Cygwin 1.7.25 issue: Crontab on Windows (was ...1.5.25...)
- From: Warren Young <warren at etr-usa dot com>
- To: Cygwin-L <cygwin at cygwin dot com>
- Date: Tue, 26 Nov 2013 09:59:42 -0700
- Subject: Re: Cygwin 1.7.25 issue: Crontab on Windows (was ...1.5.25...)
- Authentication-results: sourceware.org; auth=none
- References: <CAMwOpcry6fkHwZC8thRjMuV=iZL3keP3SCrsjCroqWrEcQNa-w at mail dot gmail dot com> <CAMwOpcp4heAtgg7fnMXdSw02iKO+Z5pwnBDC2GV6_zcLdjt_ag at mail dot gmail dot com>
On 11/26/2013 02:27, Aleksander Panayotov wrote:
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.
The standard solution here is to set your installer to require UAC.
There's a flag for this in MSI, and probably in any other reasonable
software installation system. That elevates the actual install process
to Admin privileges, so that when it launches cygrunsrv, it will have
the permissions it needs to handle the -u flag correctly.
I would suggest not shipping a private copy of Cygwin, but instead ship
Cygwin's setup.exe and do your custom minimal installation via its
command line interface. That way, you don't have to keep your shipped
version up-to-date, you don't have to worry about source code
distribution for anything but setup.exe, and you can take advantage of
the auto-UAC features of setup.exe.
That latter feature might be enough to sway you all by itself. It means
you can run the installation as a normal user, but if they have the
ability to do UAC authentication, Cygwin's setup.exe will elevate *that
part* of the installation to Admin level automatically.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple