Log File Question

We use kermit to move files from system to system on our WAN and have
been very pleased with it.

When running our kermit scripts from K95 console, the log file is
appended normally. However when we run the same script from windows XP
scheduled task, the logs are not appended, but the script runs fine
otherwise. I discovered that the the log file names we were using
("upload.log" and "ri_transfer.log") were the issue. When I changed
the log file names to "blah.log" they worked fine in both the scheduled
task and from the console.

Are there any rules about how log files should be named? Am I crazy?

I am running Kermit 95, version 2.1.3, on Windows XP Pro SP1.
Thanks.
Wes

On 2005-01-19, Wes <wes.mckellar@gmail.com> wrote:
: We use kermit to move files from system to system on our WAN and have
: been very pleased with it.
:
: When running our kermit scripts from K95 console, the log file is
: appended normally. However when we run the same script from windows XP
: scheduled task, the logs are not appended, but the script runs fine
: otherwise. I discovered that the the log file names we were using
: ("upload.log" and "ri_transfer.log") were the issue. When I changed
: the log file names to "blah.log" they worked fine in both the scheduled
: task and from the console.
:
Not in Kermit. The only issue might be whether the Windows permissions
(and other accessibility criteria, such as owner) on upload.log are
different from those on blah.log Could be that "Windows" cares more
about this than "DOS" -- i.e. the Console environment might not have access
the extra file info and so merrily allows appending even if the permissions
forbid it. Just a guess. Anything can happen in Windows, and usually
does.
[color=blue]
> Am I crazy?
>[/color]
I hope not!
[color=blue]
> I am running Kermit 95, version 2.1.3, on Windows XP Pro SP1.[/color]

I'd say all's well that ends well.

- Frank

When running as a scheduled task K95 is running under the SYSTEM
account. There should not be any restrictions on what file names
can be used from the SYSTEM account. Using LOG DEBUG, CLOSE DEBUG
around the script creation might produce some entries in the
resulting debug.log file which could point in the reason for the
denial.

Jeffrey Altman


Wes wrote:[color=blue]
> We use kermit to move files from system to system on our WAN and have
> been very pleased with it.
>
> When running our kermit scripts from K95 console, the log file is
> appended normally. However when we run the same script from windows XP
> scheduled task, the logs are not appended, but the script runs fine
> otherwise. I discovered that the the log file names we were using
> ("upload.log" and "ri_transfer.log") were the issue. When I changed
> the log file names to "blah.log" they worked fine in both the scheduled
> task and from the console.
>
> Are there any rules about how log files should be named? Am I crazy?
>
> I am running Kermit 95, version 2.1.3, on Windows XP Pro SP1.
> Thanks.
> Wes
>[/color]

--
-----------------
This e-mail account is not read on a regular basis.
Please send private responses to jaltman at mit dot edu

Wes wrote:[color=blue]
>
> When running our kermit scripts from K95 console, the log file is
> appended normally. However when we run the same script from windows[/color]
XP[color=blue]
> scheduled task, the logs are not appended, but the script runs fine
> otherwise. I discovered that the the log file names we were using
> ("upload.log" and "ri_transfer.log") were the issue. When I changed
> the log file names to "blah.log" they worked fine in both the[/color]
scheduled[color=blue]
> task and from the console.
>
> Are there any rules about how log files should be named? Am I crazy?
>
> I am running Kermit 95, version 2.1.3, on Windows XP Pro SP1.[/color]

The Windows system event viewer logs might give you some information.

--
Mark Sapiro msapiro at value net The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan