No errors in the log if the target does not exist

nnCron and nnCron LITE discussion

No errors in the log if the target does not exist

Postby arsphl » Wed, 13 Apr 2005, 14:40

Hi,

Just ran on a tipo in a script name. nnCron did not raise an alert. Here an exemple line of cron.tab

Code: Select all
*/1 * * * * "ZD:\pla\test\test_cron.bat >> d:\temp\test.txt"


Here is the cron.out

Code: Select all
nnCron LITE. v 1.11 Build 80 3.03.2003
Copyright (C) 2000-2005 nnSoft. e-mail:nemtsev@nncron.ru


And here is an extract of the log

Code: Select all
13:11:00 307 Start: "ZD:\pla\test\test_cron.bat >> d:\temp\test.txt"
13:11:00 307 Start result: 0
13:12:00 341 Start: "ZD:\pla\test\test_cron.bat >> d:\temp\test.txt"
13:12:00 341 Start result: 0
13:13:00 42 Start: "ZD:\pla\test\test_cron.bat >> d:\temp\test.txt"
13:13:00 42 Start result: 0
13:14:00 171 Start: "ZD:\pla\test\test_cron.bat >> d:\temp\test.txt"
13:14:00 171 Start result: 0
13:15:00 294 Start: "ZD:\pla\test\test_cron.bat >> d:\temp\test.txt"
13:15:00 294 Start result: 0


The D:\temp\test.txt clearly does not get created.

:) Cheers
arsphl
 
Posts: 1
Joined: Wed, 13 Apr 2005, 14:32
Location: Madrid

Postby VK » Wed, 13 Apr 2005, 16:42

First, I highly recommend you to update your nnCron LITE.
Second, nothing wrong with your example. The bat-files are started by command interpreter (cmd.exe or command.com). So, even if you made an typo in bat-file name, the command interpreter started successfully and this is what you see in the logs.

If you want to use the ouput redirection, just use cmd.exe explicitely, like this:
Code: Select all
*/1 * * * * cmd.exe /c D:\pla\test\test_cron.bat >> d:\temp\test.txt

HTH!
CU
VK
User avatar
VK
 
Posts: 680
Joined: Wed, 14 Jul 2004, 19:17


Return to nnCron forum (English)

Who is online

Users browsing this forum: No registered users and 1 guest

cron