Re: cron error can't switch user context
Le 17/04/2010 01:43, Tom Schutter a écrit :
On Fri 2010-04-16 17:06, Cyrille Lefevre wrote:
Le 16/04/2010 20:42, Tom Schutter a écrit :
http://www.cygwin.com/acronyms/#PCYMTWLL
I have number of machines running Windows2003 and Cygwin 1.7.5. On most cron
works. But on one (lemon) it does not. It appears that on lemon cron cannot
switch the user context.
Cronevents on lemon shows:
2010/04/15 17:19:01 [SYSTEM] /usr/sbin/cron: PID 656: (tschutter) CMD
(/usr/bin/python /cygdrive/f/production-sync/production-sync.py)
2010/04/15 17:19:01 [SYSTEM] /usr/sbin/cron: PID 656: (CRON) error (can't
switch user context)
/var/log/cron.log is empty on all machines.
let's configure syslogd from inetutils to have some logs :
syslogd-config --yes
I don't have a syslogd-config. Ok. So I installed inetutils. Now I have a
syslogd-config which I have just run. And I have started syslogd.
After setting up syslogd, I still see an empty /var/log/cron.log and
/var/log/messages.
did you restart cron ?
here is my log for an * * * * * date /tmp/date.log entry :
Apr 17 12:20:40 MV0213 /usr/sbin/cron: PID 2668: (CRON) STARTUP (V5.0)
Apr 17 12:20:41 MV0213 cron: PID 3364: `cron' service started
Apr 17 12:21:01 MV0213 /usr/sbin/cron: PID 3064: (root) CMD (date
/tmp/date.log)
you may need to configure sshd before to have the right permissions
on /var/empty, etc. (ssh-host-config --yes --user ${CYGSERVER_USER}
--pwd ${CYGSERVER_PASS} where CYGSERVER_USER=cyg_server and
CYGSERVER_PASS=whatever you want)
I am not sure what sshd has to do with cron.
IFAIK, if you configure cron w/o configure ssh first, cron-diagnose will
break.
In my case sshd cannot run as the cygserver user because it must be a
domain user.
under 2K3, I'm running sshd w/ a local cyg_server account + lsa + passwd
-R w/o problems whatever the passwordless account is local admin or not
or domain lambda user. not tried using a domain admin since I don't have
access to a domain admin account. however, a local admin is sufficient
to stop/start services, etc. so, a domain admin isn't required...
PS : well, I prefer the legacy one than the ng one...
PS2: IMHO, linux^Wcygwin cron(^W^Wlinux) sucks bcoz it doesn't report on
tasks return codes as a true unix does... (i.e.: root 1331 c Tue Feb
2 17:32:36 MET 2010 rc=1)
The cron daemon is running as SYSTEM on all machines.
2K3 may need to be running under cyg_server ?
Why? I have not seen any doc stating that.
to configure cron, I use :
cron-config EOF
yes
no
no
no
${CYGSERVER_PASS}
${CYGSERVER_PASS}
no
EOF
PS : doesn't support csih yet :-(
Your yes and no responses do not match what cron-config asks me:
lemon:/$ cron-config
Do you want to install the cron daemon as a service? (yes/no) yes
Enter the value of CYGWIN for the daemon: [ ]
You must decide under what account the cron daemon will run.
If you are the only user on this machine, the daemon can run as yourself.
This gives access to all network drives but only allows you as user.
To run multiple users, cron must change user context without knowing
the passwords. There are three methods to do that, as explained in
http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd1
If all the cron users have executed passwd -R (see man passwd),
which provides access to network drives, or if you are using the
cyglsa package, then cron should run under the local system account.
Otherwise you need to have or to create a privileged account.
This script will help you do so.
Do you want the cron daemon to run as yourself? (yes/no) no
Were the passwords of all cron users saved with passwd -R, or
are you using the cyglsa package ? (yes/no) yes
try to answer no, here, then, you will be asked for cyg_server
password... and may still use passwd -R :-)
The cron daemon will run as SYSTEM.
Running cron_diagnose ...
... no problem found.
Do you want to start the cron daemon as a service now? (yes/no) yes
OK. The cron daemon is now running.
well, the last no is because I prefer to launch the service myself :-)
snip
lemon:/$
It appears that cron-config decides to run cron under the SYSTEM account
because I indicated that I was using cyglsa.
cyglsa is running on all machines.
did you reboot after configuring cyglsa ?
cygserver is not running on any machine.
2K3 may need cygserver as well as passwd -D?
s/-D/-R/ sorry
If I do a passwd -R, cron will work. But I don't want to do a passwd -R.
I am forced to change my password every 60 days. Then I would have to go to every cygwin box and
change the password there as well.
don't know how to make things work w/o passwd -R, sorry.
however, an ssh net user user passwd is not so hard to do :-)
alternative, if using a local account is net user user /expire:no
snip
Regards,
Cyrille Lefevre
--
mailto:cyrille.lefevre-li...@laposte.net
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq
cron error can't switch user context
I have number of machines running Windows2003 and Cygwin 1.7.5. On most cron works. But on one (lemon) it does not. It appears that on lemon cron cannot switch the user context. Cronevents on lemon shows: 2010/04/15 17:19:01 [SYSTEM] /usr/sbin/cron: PID 656: (tschutter) CMD (/usr/bin/python /cygdrive/f/production-sync/production-sync.py) 2010/04/15 17:19:01 [SYSTEM] /usr/sbin/cron: PID 656: (CRON) error (can't switch user context) /var/log/cron.log is empty on all machines. The cron daemon is running as SYSTEM on all machines. cyglsa is running on all machines. cygserver is not running on any machine. I have rerun cron-config, rebooted, etc. I have searched the net, but most solutions seem to involve Cygwin 1.5 and no cyglsa. Does anyone have any suggestions? -- Tom Schutter First American Spatial Solutions 303-440-7272 x6822 512-977-6822 -- 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
Re: cron error can't switch user context
I have attached cronbug.txt as per the cron-config instructions. Note that the original cronbug.txt was over 5MB. I edited cronbug.txt and removed 46000 lines of cronevents output. Is there any way of cleaning out old cron entries from the event log? On Fri 2010-04-16 13:42, Tom Schutter wrote: I have number of machines running Windows2003 and Cygwin 1.7.5. On most cron works. But on one (lemon) it does not. It appears that on lemon cron cannot switch the user context. Cronevents on lemon shows: 2010/04/15 17:19:01 [SYSTEM] /usr/sbin/cron: PID 656: (tschutter) CMD (/usr/bin/python /cygdrive/f/production-sync/production-sync.py) 2010/04/15 17:19:01 [SYSTEM] /usr/sbin/cron: PID 656: (CRON) error (can't switch user context) /var/log/cron.log is empty on all machines. The cron daemon is running as SYSTEM on all machines. cyglsa is running on all machines. cygserver is not running on any machine. I have rerun cron-config, rebooted, etc. I have searched the net, but most solutions seem to involve Cygwin 1.5 and no cyglsa. Does anyone have any suggestions? -- Tom Schutter First American Spatial Solutions 303-440-7272 x6822 512-977-6822 -- 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 -- Tom Schutter First American Spatial Solutions 303-440-7272 x6822 512-977-6822 Current version -rwxr-xr-x 1 tschutter Administrators 5304 2010-02-15 19:14 /usr/share/doc/Cygwin/cron-4.1-59.README Running crons: 318017483180 1904? 18 17:17:27 /usr/sbin/cron Sendmail: lrwxrwxrwx 1 tschutter Domain Users 16 2010-03-11 11:28 /usr/sbin/sendmail - /usr/bin/cronlog Crontabs: -rw-r- 1 tschutter Administrators 355 2010-03-11 12:43 /var/cron/tabs/tschutter -rw-r- 1 18718 544 355 2010-03-11 12:43 /var/cron/tabs/tschutter cron.log: -rw-r--r-- 1 SYSTEM Administrators 0 2010-04-15 17:17 /var/log/cron.log cron.pid: -rw-r--r-- 1 SYSTEM Administrators 5 2010-04-15 17:17 /var/run/cron.pid Crontab: # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/tmp/crontab.txt installed on Thu Mar 11 12:43:48 2010) # (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie Exp $) * * * * * /usr/bin/python /cygdrive/f/production-sync/production-sync.py 0 * * * * /usr/bin/python /cygdrive/f/Logs/logrotate.py /cygdrive/f/Logs/logrotate.ini Windows Application Events log: 2010/03/25 18:51:01 [SYSTEM] /usr/sbin/cron: PID 968: (tschutter) CMD (/usr/bin/python /cygdrive/f/production-sync/production-sync.py) 2010/03/25 18:52:01 [SYSTEM] /usr/sbin/cron: PID 4216: (tschutter) CMD (/usr/bin/python /cygdrive/f/production-sync/production-sync.py) REMOVED 46000 lines of similar stuff 2010/04/16 13:10:01 [SYSTEM] /usr/sbin/cron: PID 4000: (CRON) error (can't switch user context) 2010/04/16 13:11:01 [SYSTEM] /usr/sbin/cron: PID 3496: (tschutter) CMD (/usr/bin/python /cygdrive/f/production-sync/production-sync.py) 2010/04/16 13:11:01 [SYSTEM] /usr/sbin/cron: PID 3496: (CRON) error (can't switch user context) 2010/04/16 13:12:01 [SYSTEM] /usr/sbin/cron: PID 204: (tschutter) CMD (/usr/bin/python /cygdrive/f/production-sync/production-sync.py) 2010/04/16 13:12:01 [SYSTEM] /usr/sbin/cron: PID 204: (CRON) error (can't switch user context) 2010/04/16 13:13:01 [SYSTEM] /usr/sbin/cron: PID 832: (tschutter) CMD (/usr/bin/python /cygdrive/f/production-sync/production-sync.py) 2010/04/16 13:13:01 [SYSTEM] /usr/sbin/cron: PID 832: (CRON) error (can't switch user context) 2010/04/16 13:13:04 [tschutter] crontab: PID 3624: (tschutter) LIST (tschutter) Cygcheck: Cygwin Configuration Diagnostics Current System Time: Fri Apr 16 13:13:29 2010 Windows 2003 Server R2 Ver 5.2 Build 3790 Service Pack 2 Running in Terminal Service session Path: C:\cygwin\home\tschutter\bin C:\cygwin\usr\sbin C:\cygwin\sbin C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\WINDOWS\system32 C:\WINDOWS C:\WINDOWS\System32\Wbem C:\Program Files\WinZip C:\Program Files\Dell\SysMgt\oma\bin C:\Program Files\Dell\SysMgt\oma\oldiags\bin C:\WINDOWS\system32\WindowsPowerShell\v1.0 C:\Program Files\Python26 F:\PxPoint\bin F:\WebSites\bin F:\WebSites\PxView\bin C:\Program Files\MySQL\MySQL Server 5.0\bin Output from C:\cygwin\bin\id.exe UID: 18718(tschutter)GID: 10513(Domain Users) 10513(Domain Users) 544(Administrators) 545(Users) 27644(FDSV-DL-FASS) 16577(FDSV-DL-Proxix)25442(FDSV-GG-Bugzilla) 28483(FDSV-GG-FASS) 25443(FDSV-GG-Jabber) 25446(FDSV-GG-Nagios)18189(FDSV-GG-PrxAAPCAdmins) 18169(FDSV-GG-PrxBLD)22611(FDSV-GG-PrxPCAdmins) 28484(FDSV-GG-ShareFASSSharedRW) 25387(FDSV-GG
Re: cron error can't switch user context
- Original Message - From: Tom Schutter To: cygwin Sent: Friday, April 16, 2010 15:29 |I have attached cronbug.txt as per the cron-config instructions. | | Note that the original cronbug.txt was over 5MB. I edited cronbug.txt and removed 46000 lines of cronevents output. Is there any way of cleaning out old cron entries from the event log? | | On Fri 2010-04-16 13:42, Tom Schutter wrote: | I have number of machines running Windows2003 and Cygwin 1.7.5. On most cron works. But on one (lemon) it does not. It appears that on lemon cron cannot switch the user context. | | Cronevents on lemon shows: | | 2010/04/15 17:19:01 [SYSTEM] /usr/sbin/cron: PID 656: (tschutter) CMD (/usr/bin/python /cygdrive/f/production-sync/production-sync.py) | 2010/04/15 17:19:01 [SYSTEM] /usr/sbin/cron: PID 656: (CRON) error (can't switch user context) | | /var/log/cron.log is empty on all machines. | | The cron daemon is running as SYSTEM on all machines. | | cyglsa is running on all machines. | Hi, I should perhaps modify cronbug to use tail with cronevents, but it's unusual to see a report that cron is broken yet there are 46000 lines in the log! I assume cron used to work, then something happened and it stopped working. Or there is something special about the tschutter account. Can you identify the something ? Any difference between the lemon and the others? It's most likly not a cron problem, but something to do with cyglsa. I have never used it, don't have a system like yours to test and there is no such previous report. So not sure what to recommend. Does password-less ssh work for tschutter ? If you can't identify the something, you could try to strace cron on the lemon and on another machine. Here is the recipe. 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 Restart cron Pierre -- 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
Re: cron error can't switch user context
Le 16/04/2010 20:42, Tom Schutter a écrit :
I have number of machines running Windows2003 and Cygwin 1.7.5. On most cron
works. But on one (lemon) it does not. It appears that on lemon cron cannot
switch the user context.
Cronevents on lemon shows:
2010/04/15 17:19:01 [SYSTEM] /usr/sbin/cron: PID 656: (tschutter) CMD
(/usr/bin/python /cygdrive/f/production-sync/production-sync.py)
2010/04/15 17:19:01 [SYSTEM] /usr/sbin/cron: PID 656: (CRON) error (can't
switch user context)
/var/log/cron.log is empty on all machines.
let's configure syslogd from inetutils to have some logs :
syslogd-config --yes
you may need to configure sshd before to have the right permissions
on /var/empty, etc. (ssh-host-config --yes --user ${CYGSERVER_USER}
--pwd ${CYGSERVER_PASS} where CYGSERVER_USER=cyg_server and
CYGSERVER_PASS=whatever you want)
PS : well, I prefer the legacy one than the ng one...
PS2: IMHO, linux^Wcygwin cron(^W^Wlinux) sucks bcoz it doesn't report on
tasks return codes as a true unix does... (i.e.: root 1331 c Tue Feb
2 17:32:36 MET 2010 rc=1)
The cron daemon is running as SYSTEM on all machines.
2K3 may need to be running under cyg_server ?
to configure cron, I use :
cron-config EOF
yes
no
no
no
${CYGSERVER_PASS}
${CYGSERVER_PASS}
no
EOF
PS : doesn't support csih yet :-(
cyglsa is running on all machines.
did you reboot after configuring cyglsa ?
cygserver is not running on any machine.
2K3 may need cygserver as well as passwd -D?
I have rerun cron-config, rebooted, etc.
well, ok, you surelly have rebooted :-)
I have searched the net, but most solutions seem to involve Cygwin 1.5 and no
cyglsa.
Does anyone have any suggestions?
done.
Cordialement,
Cyrille Lefevre
--
mailto:cyrille.lefevre-li...@laposte.net
--
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
Re: cron error can't switch user context
Le 17/04/2010 00:06, Cyrille Lefevre a écrit : cygserver is not running on any machine. 2K3 may need cygserver as well as passwd -D? s/-D/-R/ sorry Cordialement, Cyrille Lefevre -- mailto:cyrille.lefevre-li...@laposte.net -- 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
Re: cron error can't switch user context
On Fri 2010-04-16 17:06, Cyrille Lefevre wrote:
Le 16/04/2010 20:42, Tom Schutter a écrit :
I have number of machines running Windows2003 and Cygwin 1.7.5. On most
cron works. But on one (lemon) it does not. It appears that on lemon cron
cannot switch the user context.
Cronevents on lemon shows:
2010/04/15 17:19:01 [SYSTEM] /usr/sbin/cron: PID 656: (tschutter) CMD
(/usr/bin/python /cygdrive/f/production-sync/production-sync.py)
2010/04/15 17:19:01 [SYSTEM] /usr/sbin/cron: PID 656: (CRON) error (can't
switch user context)
/var/log/cron.log is empty on all machines.
let's configure syslogd from inetutils to have some logs :
syslogd-config --yes
I don't have a syslogd-config. Ok. So I installed inetutils. Now I have a
syslogd-config which I have just run. And I have started syslogd.
After setting up syslogd, I still see an empty /var/log/cron.log and
/var/log/messages.
you may need to configure sshd before to have the right permissions
on /var/empty, etc. (ssh-host-config --yes --user ${CYGSERVER_USER}
--pwd ${CYGSERVER_PASS} where CYGSERVER_USER=cyg_server and
CYGSERVER_PASS=whatever you want)
I am not sure what sshd has to do with cron. In my case sshd cannot run as the
cygserver user because it must be a domain user.
PS : well, I prefer the legacy one than the ng one...
PS2: IMHO, linux^Wcygwin cron(^W^Wlinux) sucks bcoz it doesn't report on
tasks return codes as a true unix does... (i.e.: root 1331 c Tue Feb
2 17:32:36 MET 2010 rc=1)
The cron daemon is running as SYSTEM on all machines.
2K3 may need to be running under cyg_server ?
Why? I have not seen any doc stating that.
to configure cron, I use :
cron-config EOF
yes
no
no
no
${CYGSERVER_PASS}
${CYGSERVER_PASS}
no
EOF
PS : doesn't support csih yet :-(
Your yes and no responses do not match what cron-config asks me:
lemon:/$ cron-config
Do you want to install the cron daemon as a service? (yes/no) yes
Enter the value of CYGWIN for the daemon: [ ]
You must decide under what account the cron daemon will run.
If you are the only user on this machine, the daemon can run as yourself.
This gives access to all network drives but only allows you as user.
To run multiple users, cron must change user context without knowing
the passwords. There are three methods to do that, as explained in
http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd1
If all the cron users have executed passwd -R (see man passwd),
which provides access to network drives, or if you are using the
cyglsa package, then cron should run under the local system account.
Otherwise you need to have or to create a privileged account.
This script will help you do so.
Do you want the cron daemon to run as yourself? (yes/no) no
Were the passwords of all cron users saved with passwd -R, or
are you using the cyglsa package ? (yes/no) yes
The cron daemon will run as SYSTEM.
Running cron_diagnose ...
... no problem found.
Do you want to start the cron daemon as a service now? (yes/no) yes
OK. The cron daemon is now running.
In case of problem, examine the log file for cron,
/var/log/cron.log, and the appropriate syslog file
for information about the problem cron is having.
Examine also any cron.log file in the HOME directory
(or the file specified in MAILTO) and cron related files in /tmp.
If you cannot fix the problem, then report it to cyg...@cygwin.com.
Please run the script /usr/bin/cronbug and ATTACH its output
(the file cronbug.txt) to your e-mail.
WARNING: PATH may be set differently under cron than in interactive shells.
Names such as find and date may refer to Windows programs.
lemon:/$
It appears that cron-config decides to run cron under the SYSTEM account
because I indicated that I was using cyglsa.
cyglsa is running on all machines.
did you reboot after configuring cyglsa ?
cygserver is not running on any machine.
2K3 may need cygserver as well as passwd -D?
If I do a passwd -R, cron will work. But I don't want to do a passwd -R.
I am forced to change my password every 60 days. Then I would have to go to
every cygwin box and change the password there as well.
I have rerun cron-config, rebooted, etc.
well, ok, you surelly have rebooted :-)
I have searched the net, but most solutions seem to involve Cygwin 1.5 and
no cyglsa.
Does anyone have any suggestions?
done.
--
Tom Schutter
First American Spatial Solutions
303-440-7272 x6822
512-977-6822
--
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
(CRON) error (can't switch user context)
Hello, I have setup Cygwin and cron on two machines. On the first machine, a Windows XP, everything went OK. Cron is running and my echo statement is being written to a file. On the second machine, a Windows Vista, cron appears to be running correctly but my echo statement is not being written to my file? I ran cronbug and found in the output several '(CRON) error (can't switch user context)' messages. I have tried googling for an answer to this issue but have not had much luck. Any help would be appreciated. Thanks! Phil Current version -r-xr-x---+ 1 Admin6 Users 4959 Jun 12 2007 /usr/share/doc/Cygwin/cron-4.1-6.README Running crons: 5464 4232 5464 4184 ? 18 14:37:37 /usr/sbin/cron Sendmail: lrwxrwxrwx 1 Admin6 None 16 Jul 19 12:34 /usr/sbin/sendmail - /usr/bin/cronlog Crontabs: -rw-r- 1 Admin6 SYSTEM 328 Jul 19 14:06 /var/cron/tabs/Admin6 -rw-r--r-- 1 Admin6 None 291 Jul 19 14:38 /var/cron/tabs/cronbug.txt cron.log: -rw-r--r-- 1 SYSTEM SYSTEM 0 Jul 19 14:37 /var/log/cron.log cron.pid: -rw-r--r-- 1 SYSTEM SYSTEM 5 Jul 19 14:37 /var/run/cron.pid Crontab: # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/tmp/crontab.5YkWvHz2GC installed on Sat Jul 19 14:06:09 2008) # (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie Exp $) SHELL=/bin/sh * * * * * /home/Admin6/external_backup.sh * * * * * echo Wow cron is working! /home/Admin6/crontes.txt Windows Application Events log: 2008/07/19 13:34:43 [Admin6] crontab: PID 4216: (Admin6) BEGIN EDIT (Admin6) 2008/07/19 13:36:44 [Admin6] crontab: PID 4216: (Admin6) REPLACE (Admin6) 2008/07/19 13:36:44 [Admin6] crontab: PID 4216: (Admin6) END EDIT (Admin6) 2008/07/19 13:36:46 [Admin6] crontab: PID 3412: (Admin6) BEGIN EDIT (Admin6) 2008/07/19 13:36:56 [Admin6] crontab: PID 3412: (Admin6) REPLACE (Admin6) 2008/07/19 13:36:56 [Admin6] crontab: PID 3412: (Admin6) END EDIT (Admin6) 2008/07/19 13:38:03 [SYSTEM] /usr/sbin/cron: PID 3912: (CRON) STARTUP (V5.0) 2008/07/19 13:38:04 [SYSTEM] cron: PID 6016: `cron' service started 2008/07/19 13:39:01 [SYSTEM] /usr/sbin/cron: PID 2772: (Admin6) CMD ($HOME/home/Admin6/external_backup.sh) 2008/07/19 13:39:01 [SYSTEM] /usr/sbin/cron: PID 2772: (CRON) error (can't switch user context) 2008/07/19 13:40:01 [SYSTEM] /usr/sbin/cron: PID 4900: (Admin6) CMD ($HOME/home/Admin6/external_backup.sh) 2008/07/19 13:40:01 [SYSTEM] /usr/sbin/cron: PID 4900: (CRON) error (can't switch user context) 2008/07/19 13:40:33 [Admin6] crontab: PID 5892: (Admin6) BEGIN EDIT (Admin6) 2008/07/19 13:40:47 [Admin6] crontab: PID 5892: (Admin6) REPLACE (Admin6) 2008/07/19 13:40:47 [Admin6] crontab: PID 5892: (Admin6) END EDIT (Admin6) 2008/07/19 13:40:59 [Admin6] crontab: PID 3612: (Admin6) BEGIN EDIT (Admin6) 2008/07/19 13:41:01 [SYSTEM] /usr/sbin/cron: PID 3912: (Admin6) RELOAD (tabs/Admin6) 2008/07/19 13:41:01 [SYSTEM] /usr/sbin/cron: PID 4160: (Admin6) CMD ($HOME/home/Admin6/external_backup.sh) 2008/07/19 13:41:02 [SYSTEM] /usr/sbin/cron: PID 4160: (CRON) error (can't switch user context) 2008/07/19 13:42:01 [SYSTEM] /usr/sbin/cron: PID 3760: (Admin6) CMD (/home/Admin6/external_backup.sh) 2008/07/19 13:42:01 [SYSTEM] /usr/sbin/cron: PID 3760: (CRON) error (can't switch user context) (Admin6) 2008/07/19 14:33:47 [Admin6] crontab: PID 4364: (Admin6) LIST (Admin6) 2008/07/19 14:37:37 [SYSTEM] /usr/sbin/cron: PID 5464: (CRON) STARTUP (V5.0) 2008/07/19 14:37:37 [SYSTEM] /usr/sbin/cron: PID 5464: (cronbug.txt) ORPHAN (no passwd entry) 2008/07/19 14:37:38 [SYSTEM] cron: PID 4232: `cron' service started 2008/07/19 14:38:01 [SYSTEM] /usr/sbin/cron: PID 4332: (Admin6) CMD (echo Wow cron is working! /home/Admin6/crontes.txt) 2008/07/19 14:38:01 [SYSTEM] /usr/sbin/cron: PID 4332: (CRON) error (can't switch user context) 2008/07/19 14:38:01 [SYSTEM] /usr/sbin/cron: PID 1316: (Admin6) CMD (/home/Admin6/external_backup.sh) 2008/07/19 14:38:01 [SYSTEM] /usr/sbin/cron: PID 1316: (CRON) error (can't switch user context) 2008/07/19 14:38:23 [Admin6] crontab: PID 5348: (Admin6) LIST (Admin6) Cygcheck: Cygwin Configuration Diagnostics Current System Time: Sat Jul 19 14:38:24 2008 Windows Longhorn/Vista (not yet supported!) Ver 6.0 Build 6000 Path: C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\cygwin\usr\X11R6\bin c:\Windows\system32 c:\Windows c:\Windows\System32\Wbem c:\hp\bin\Python c:\Program Files\Common Files\Roxio Shared\DLLShared\ c:\Program Files\Common Files\Roxio Shared\DLLShared\ c:\Program Files\Common Files\Roxio Shared\9.0\DLLShared\ SysDir: C:\Windows\system32 WinDir: C:\Windows USER = 'Admin6' PWD = '/var/cron/tabs' CYGWIN = 'ntsec' HOME = '/home/Admin6' MAKE_MODE = 'unix' HOMEPATH = '\Users\Admin6' APPDATA = 'C:\Users\Admin6\AppData\Roaming' MANPATH = '/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man' HOSTNAME = 'Admin6-PC' ONLINESERVICES = 'Online Services' PROCESSOR_IDENTIFIER = 'x86 Family 15 Model 107 Stepping 1, AuthenticAMD' ROXIOCENTRAL = 'c:\Program Files\Common Files
