Page 1 of 1

Log file - xattr

Posted: 30 May 2017, 18:48
by kim
why does this not work anymore using 4.7.10 portable ?
filebot.cmd -script fn:xattr "path" --log-file "path\context.log"
OR
filebot.cmd -script fn:xattr --action clear "path" --log-file "path\context.log"

info on screen is ok, but only "Done ヾ(@⌒ー⌒@)ノ" in log file

EDIT: 4.7.7 = OK , 4.7.8+ = problem

Re: Log file - xattr

Posted: 31 May 2017, 02:32
by rednoah
STDIO is different from logging. It's always been different, but now it's more different. If you want the full console output written to file, then it's best to use IO redirection, because that'll catch output that logging could not catch (such as JVM errors, FileBot itself crashing, libmediainfo crashing, etc).

I'll update the script to use logging instead of STDIO output.

Re: Log file - xattr

Posted: 01 Jun 2017, 17:02
by kim
thx, that fixed the xattr log output

but there is a problem more (for me at least):
You wrote this:
"In the portable distribution, FileBot.exe is the GUI application, and filebot.cmd is the console application. You'll need to make sure that you use the console application, if you want to see console output."
viewtopic.php?t=3138#p17477

filebot.cmd runs ok if only 1 command line, but I use multiple groovy scripts from a bat file = break / quit after the first command line, if I use the filebot.portable.launcher.exe instead of filebot.cmd it works OK, but log gets this line all the time "Using persistent disk cache D:\_DoWnLoaD\FileBot_4.7.10-portable\data\cache\1"

EDIT: the "Using persistent disk cache D:\_DoWnLoaD\FileBot_4.7.10-portable\data\cache\1" part was because of "-Dnet.filebot.logging.debug=ALL" in the ini and not in the filebot.cmd

Re: Log file - xattr

Posted: 02 Jun 2017, 02:51
by rednoah
1.
I've updated the xattr script. You can use -script dev:xattr for now which now uses logging instead of plain STDIO.


2.
That's just how CMD/BAT scripts work. You need to use the call command if you want to call a bat script inside a bat script. It makes no sense. I recommend using PowerShell or Groovy for everything and avoiding CMD/BAT whenever possible.

@see https://stackoverflow.com/questions/116 ... -line-exit