Open GoogleCodeExporter opened 9 years ago
You can log errors to the log file, or another log file using 2> :
fbclone -v ... > allfine.log 2> errors.log
or
fbclone -v ... > clone.log 2>&1
2>&1 redirects the error output descriptor to standard output descriptor
Original comment by pierr...@gmail.com
on 9 Nov 2012 at 12:14
Sorry the delay. I was not working in this project for long time, but I getting
back on it now.
I think I couldn't express myself well (maybe, because English is not my first
language :) )
I know how to use redirection... It was that " >> fbclone.log" that generated
the log file I had attached before.
Do you took a look into that file? It's trunked. That's why I had written: "...
but only a small and initial part is logged - I don't know why"
Don't you think that these fragment of report - that I saw on screen - should
be inside of the log file?
Please consider spend two and a half minutes and watch this video I recorded:
http://youtu.be/cvazg32ff9w
/Micheus
Original comment by mich...@gmail.com
on 13 Feb 2013 at 6:56
[deleted comment]
Thanks for your advice Pierre !
fbclone -v ... > allfine.log 2> errors.log
got general log in allfine and errors in errors. worked perfect for me !
Original comment by marianne...@gmail.com
on 28 Feb 2013 at 8:57
Pierre, my apologies, I got back to that project and I finally discover that I
was using a wrong parameter for charset:
>> 1. fbclone -v -s SIGAA.FDB -su SYSDBA -sp masterkey -t sigaa_utf.fdb -tu
SYSDBA -tp masterkey -tc UTF8 -rc WIN1252 -wc UTF8 >> fbclone.log
they should be:
>>... -tc UTF8 -rc NONE -wc WIN1252
as you post in your Wiki doc (that I didn't see before, I don't know why).
Thank you for share this useful tool.
/Micheus
Original comment by mich...@gmail.com
on 12 Jun 2013 at 12:46
Original issue reported on code.google.com by
mich...@gmail.com
on 8 Aug 2012 at 10:14Attachments: