This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: empty cron.log

Hello to everyone following along.
Pierre and I worked off-line on this problem.
We didn't yet figure out how to run cron as self (using cron-config and specifying self) on Windows 10 with a Microsoft Id. We did figure out another approach though that does work on Windows 10 with a Microsoft Id:

1) install cywin inetutils, cron
2) Start a cygwin window as administrator
3) Run
   ssh-host-config  -y
. We don't actually need it to set up a sshd daemon/service, but this script creates a privileged cyg_server account on the machine that is configured in a way that we can use. Feel free to subsequently run
   cygrunsrv -R sshd
if you don't need sshd.
4) Now run cron-config. If it asks, have it stop the running crond. Tell it you do want it create a service. You probably want to specify a blank string for the CYGWIN value, aka, just hit Enter. When asked if the crond should run as self, say "no". When asked if passwd -R will be set up for all id's, say "no". It should then recognize that the cyg_server account should work. It will ask you if you want to specify an account other than that. Answer "no". If it warns you about the /var /var/cron and /var/cron/tabs permissions, you can probably ignore that and continue. You can tell it to go ahead and start the crond service. 5) As usual, you'll still need to run crontab to tell crond what it should run for you.
I think that's about it.

Good luck everyone.


On 12/18/2015 2:34 PM, Pierre A Humblet wrote:
-----Original Message-----
From:  Jason Crawford
Sent: Friday, December 18, 2015 1:01 PM

On 12/18/2015 9:50 AM, Pierre A Humblet wrote:
-----Original Message-----
From: Jason Crawford
Sent: Friday, December 18, 2015 2:17 AM

Hello everyone,
      Thanks for a great offering and all the help you provide.    I've
used cygwin for a few years, but not deeply.  cron is one of the tools I
find very handy.   Recently I upgraded to Windows 10 and ran in to
problems on my Surface Pro 3.   I installed cygwin cron (latest cygwin
32bit (2.873).  Cron is 4.1-63.) and it seemed to work but as soon as
I switched my laptop to use the Microsoft ID cron as Microsoft suggest,
cron stopped working, complaining that it can not switch id's.   If I do
a fresh install of Win10, switch to the Microsoft ID, and install cygwin
and cron, cron won't even work once.   And if I do a fresh install of
Win10 and never switch to the Microsoft id, cygwin cron works fine.
When it fails, the cronevents log file complains that it can't switch user
I really don't do much.  I just install cygwin with cron, emacs, ssh,
inetutils, unison, wget.  Then I start up a cygwin window as
administrator.   Then cron-config, yes (service), [] (blank CYGWIN),
yes (self), yes (start daemon).   Then I create a trivial cron file "*/1
* * * *  date >~/cron_is_running.txt".   crontab mycron     ... and I
wait a minute.  Then I invoke cronevents.

I want to try out all the features of that Microsoft touts as coming
with use of the Microsoft ID, but I don't want to lose cron.

What do we all suggest that I do next?
Is that only with Cron or also with other services such as passwordless
I don't run sshd on the machine (as far as I know).  I only ssh out.
That works fine without a password.   But...

But I've just tried setting up sshd on two Windows machines just now.
I ran in to a few complications due to being a novice, but it eventually
worked on Windows 7.    I've still not gotten sshd to work on Windows 10
if my ssh client is on another machine.  That seems to be some sort of
network connection or firewall problem.  I can ssh from the local Win10
machine to the local Win10 machine though.   I have only one account and
I can ssh in to that without a password using authorized_keys.

Does that answer your question?   Is there a simpler or more helpful way
that I can gather data for you?   I don't mind reinstalling the
operating system if that would help.
Thanks, Jason.

I assume both cron-config and ssh-host-config asked you for the name of a privileged user,
and you used the same name in both cases.

You may want to try what I suggested to someone else a while ago

The instructions were, as follows, except that now the service should run under the privileged account,
(use -u), not under SYSTEM (the default)

Stop the cron service.
Use a simple crontab that runs every minute, for only one user.
Using cygrunsrv, create a new service runing "strace" with argument "cron" under SYSTEM
1)  cygrunsrv -I trace_cron -p /usr/bin/strace -a /usr/sbin/cron
2)  cygrunsrv -S trace_cron
3)  Let this run for no more than 2 minutes, output will be in /var/log/trace_cron.log
      You may have to use kill -9 to stop the service (kill the cron pid)
4)  Send the trace_cron.log file as an attachment.
5)  Remove the trace_cron service


Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]