Subj : Re: capturing tool output
To   : Digital Man
From : Rampage
Date : Sun Jan 06 2019 12:53 am

 >   blahblah 1>>addfiles.log 2>&1

 > we'll find out once my tester gets back to me if it worked in their
 > situation...

sadly, this didn't work, either :(

----- snip -----
> The issue is happening with anything being TIC'd to me, all areas,
> all files.

> Here's the log line from a failed run:

> 1/5  10:57:38a  TICKIT Executing: 'C:\sbbs\exec\addfiles nasa -zd
> +C:\sbbs\temp\event\tickit-files.bbs 24 13 1>>C:\sbbs\temp\event\addfiles.log
> 2>&1'.

> There was no 'addfiles.log' in my \sbbs\temp\event\ directory, so I think
> there's still something not right with that redirect/append syntax...
----- snip -----

i don't understand why it isn't working...

so just to clarify, when run from an event, tickit.js executes addfiles and
addfiles fails for some unknown reason... the redirection code was added to try
to capture the addfiles output so we could see the failure but it is not
captured either...

if the above command line is copied and pasted to the terminal command prompt
OR if tickit.js is run from jsexec, then addfiles runs properly and the file is
imported into the file base...

the only difference we can see is that the temp directory is different between
the two methods of execution but that should not matter...

)\/(ark

---
 þ Synchronet þ SouthEast Star Mail HUB - SESTAR

.