On Mar 27, 8:17 am, nob...@nowhere.com (Will Renkel) wrote:
> From what you wrote it is all set to run.
> If cron is indeed running then it should trigger it
> Abiut the warning message
> it is just that - a warning
> if you use crontab -e, -l etc
> you are just fine.
> If you want too see raw data - ck /var/cron/tabs
> assuming you are using the cron that comes with Cygwin - vixie cron
>
> --
> ---------------------------------------------------------------
> Will Renkel
> Wheaton, Ill.
> REGISTERD Linux User: 300583
>
> ---------------------------------------------------------------cxbest2...@yahoo.com wrote:
>
> >Hi everyone,
> >
> >Don't know if it is the right place to post, please kindly direct me
> >to the right group if it is not proper here.
> >
> >I intend to run a cron job on Cygwin. The Cygwin runs on WinXP.
> >
> >I checked the Windows service list and found cron service is started.
> >
> >I use "crontab -e" to set up the following task,
> >
> >30 * * * * /cygwin/d/expect scriptname.exp
> >
> >I checked "crontab -l". It shows:
> >
> ># DO NOT EDIT THIS FILE - edit the master and reinstall.
> ># (/tmp/crontab.5352 installed on Mon Mar 26 12:21:31 2007)
> ># (Cron version -- $Id: crontab.c,v 1.8 2004/12/21 16:14:41 corinna
> >Exp $)
> >30 * * * * /cygwin/d/expect scriptname.exp
> >
> >I suspect it is the priviledge problem, so I type "crontab -u {myWinXP
> >login ID} -e" and it shows:
> >
> >must be privileged to use -u
> >
> >Anyone knows that is the problem? Thanks in advance.
> >
Thanks Will. It just doen't trigger anything when the expected time
comes. Yes, i am using the cron coming with Cygwin. I use
cron_diagnose.sh to diagnose it. First it tells me that I need to
"chmod +r /etc/passwd" then "chmod +r /etc/group". Now it comes to
this message.

XUCH@XUCH-1 /cygdrive/d
$ cron_diagnose.sh
cron_diagnose.sh 1.10

The owner and the Administrators need
to have .w. permission to /var/run.
Here are the current permissions:

drwxrwx---+ 2 XUCH mkgroup-l-d 0 Mar 26 09:41 /var/run

Please change the user and/or group ownership and
permissions of /var/run, and then run this script again.

I don't know how to do? Do you know? Thanks very much.

On Mar 27, 9:29 am, "Schubert" wrote:
> On Mar 27, 8:17 am, nob...@nowhere.com (Will Renkel) wrote:
>
>
>
> > From what you wrote it is all set to run.
> > If cron is indeed running then it should trigger it
> > Abiut the warning message
> > it is just that - a warning
> > if you use crontab -e, -l etc
> > you are just fine.
> > If you want too see raw data - ck /var/cron/tabs
> > assuming you are using the cron that comes with Cygwin - vixie cron
>
> > --
> > ---------------------------------------------------------------
> > Will Renkel
> > Wheaton, Ill.
> > REGISTERD Linux User: 300583
>
> > ---------------------------------------------------------------cxbest2...@yahoo.com wrote:
>
> > >Hi everyone,
>
> > >Don't know if it is the right place to post, please kindly direct me
> > >to the right group if it is not proper here.
>
> > >I intend to run a cron job on Cygwin. The Cygwin runs on WinXP.
>
> > >I checked the Windows service list and found cron service is started.
>
> > >I use "crontab -e" to set up the following task,
>
> > >30 * * * * /cygwin/d/expect scriptname.exp
>
> > >I checked "crontab -l". It shows:
>
> > ># DO NOT EDIT THIS FILE - edit the master and reinstall.
> > ># (/tmp/crontab.5352 installed on Mon Mar 26 12:21:31 2007)
> > ># (Cron version -- $Id: crontab.c,v 1.8 2004/12/21 16:14:41 corinna
> > >Exp $)
> > >30 * * * * /cygwin/d/expect scriptname.exp
>
> > >I suspect it is the priviledge problem, so I type "crontab -u {myWinXP
> > >login ID} -e" and it shows:
>
> > >must be privileged to use -u
>
> > >Anyone knows that is the problem? Thanks in advance.
>
> Thanks Will. It just doen't trigger anything when the expected time
> comes. Yes, i am using the cron coming with Cygwin. I use
> cron_diagnose.sh to diagnose it. First it tells me that I need to
> "chmod +r /etc/passwd" then "chmod +r /etc/group". Now it comes to
> this message.
>
> XUCH@XUCH-1 /cygdrive/d
> $ cron_diagnose.sh
> cron_diagnose.sh 1.10
>
> The owner and the Administrators need
> to have .w. permission to /var/run.
> Here are the current permissions:
>
> drwxrwx---+ 2 XUCH mkgroup-l-d 0 Mar 26 09:41 /var/run
>
> Please change the user and/or group ownership and
> permissions of /var/run, and then run this script again.
>
> I don't know how to do? Do you know? Thanks very much.- Hide quoted text -
>
> - Show quoted text -

OK, now i use:
$ chown -R administrators.administrators /var/run
to change the ownership , and a new message shows:

----------------------------------------------------------------------------
Here are the current permissions:

ls: cannot access /usr/sbin/sendmail: No such file or directory

Please change the user and/or group ownership and
permissions of /usr/sbin/sendmail, and then run this script again.
ssmtp and exim are suitable mailers.

This script did not find any errors in your cron setup.

If you are running cron as yourself,
/usr/sbin/sendmail should point to an executable mailer

If you are still unable to get cron to work, then try
shutting down the cron service, uninstalling it,
reinstalling it, and restarting it.

The following commands will do that:
$ cygrunsrv --stop cron
$ cygrunsrv --remove cron
$ cygrunsrv --install cron -p /usr/sbin/cron -a -D
(You can also add a -u switch)
$ cygrunsrv --start cron

If the cron service does not start, try deleting the file
/var/run/cron.pid and then repeating the commands above.

Also, examine the log file for cron, /var/log/cron.log, for
information that it might give you about the problem cron is
having.

-----------------------------------------------------------------------
Why i don't have /usr/sbin/sendmail