/usr/bin/cron-config can render a Win2K3 box unusable

Charles Wilson cygwin@cwilson.fastmail.fm
Wed Nov 17 18:46:00 GMT 2010

On 2/16/2010 5:46 PM, Charles Wilson wrote:
> Pierre A. Humblet wrote:
>> At 03:44 PM 2/16/2010, Patrick Rynhart wrote:
>>> I'm on Windows Server 2003 and carefully read through
>>> /usr/share/doc/Cygwin/cron-4.1-57.README prior to configuring cron.
>>> The guide discusses how a privileged user account is required in order
>>> to run cron.  The script  /usr/bin/cron-config gives you the option of
>>> creating a user account on behalf (e.g. cyg_server) or using your own
>>> account, i.e.
>> Good point, will do.
> Actually, this might be a csih thing... I won't be able to look into it
> until next week sometime, so...PTC.

This is not related to csih.  Neither cron-config nor exim-config use
csih at all, but could probably benefit from a rewrite that does use it.

csih only edits the rights of *newly created* account that csih, itself,
created. It won't modify the rights of any existing account AFAICT.  The
same can't be said of cron-config/exim-config apparently.  I assume,
since this thread has been dormant for so long, that whatever fix Pierre
implemented has been sufficient to fix the problem, so...


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

More information about the Cygwin mailing list