Just a guess, but... lines in unix text files must all end in a newline.
If you edited the crontab in Windows, it may have left off the final newline
unless you specifically hit Enter at the end of the last line.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Arijit Das
Sent: Wednesday, January 04, 2006 9:39 AM
To: activeperl@listserv.activestate.com; perl-unix-users@listserv.activestate.com
Subject: [Perl-unix-users] Syntax checking in crontabAppologies for asking this question in a Perl forum..But I expect lots of UNIX experts here...so am posting this question.Is there a way I can have the syntax of my crontab file checked in a Solaris System?Basically, I have a crontab file which looks perfect to me syntactically but I get mails saying that:Your "crontab" on abhay2!unexpected end of lineHere is the content of my crontab file:abhay2> crontab -l
## Added for testing if Syncing happens properly for Regressions testcases with new script
00 20 * * * /u/regress/INFRA_HOME/perforce/SyncSnapshots.csh -regr -b VCS7_1 -r /u/regress/p4_snapshots/nightly71 -l /u/regress/perforce/Regress/71sync.log ...04 20 * * * /u/regress/INFRA_HOME/perforce/Regress/syncSnapshots -r 72## New Crons for Syncing Causes Files
20 20 * * * /u/regress/INFRA_HOME/perforce/SyncSnapshots.csh -regr -b TD -r /u/regress/p4_snapshots/Causes/TD -l /u/regress/perforce/Regress/Causes_TD_sync.log CausesDir/...
20 20 * * * /u/regress/INFRA_HOME/perforce/SyncSnapshots.csh -regr -b VCS7_1 -r /u/regress/p4_snapshots/Causes/VCS7_1 -l /u/regress/perf## Added for testing if Syncing happens properly for Regressions testcases with new scriptAnybody faced this before...?Thanks,Arijit
Yahoo! Photos
Ring in the New Year with Photo Calendars. Add photos, events, holidays, whatever.
_______________________________________________ Perl-Unix-Users mailing list Perl-Unix-Users@listserv.ActiveState.com To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
