Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] How can I save the output log to a file? #3599

Closed
licklake opened this issue Aug 11, 2016 · 9 comments
Closed

[Question] How can I save the output log to a file? #3599

licklake opened this issue Aug 11, 2016 · 9 comments

Comments

@licklake
Copy link

Hi,

I would like to analyse the steps of the bot afterwards. So I need a file where every step is saved in.
How can I accomplish that?

@omeryagmurlu
Copy link

./run.sh > output.file

@licklake
Copy link
Author

licklake commented Aug 11, 2016

@omeryagmurlu nope, isn't working for me

@kestel
Copy link
Contributor

kestel commented Aug 11, 2016

./run.sh | tee -a bot.log
It will show log to stdout and also write to bot.log

@licklake
Copy link
Author

I am running on 64 bit Debian and that method isn't working

@kestel
Copy link
Contributor

kestel commented Aug 11, 2016

Any error message?

Also, you can try python ./pokecli.py -cf config/config.json | tee -a bot.log

@licklake
Copy link
Author

licklake commented Aug 11, 2016

no, that doesn't work for me... no error messages, nothing. It just shows me the output on the terminal and doesn't save anything to the file

EDIT: I just noticed that it works on the local machine, before I testet it over ssh... crazy

@kestel
Copy link
Contributor

kestel commented Aug 11, 2016

It's magic.
ls -la bot.log shows "No such file"?

@licklake
Copy link
Author

no, the file is getting created, but theres nothing in it

@RomainPrevot
Copy link

I use :
python pokecli.py --config ./configs/config.json > bot.log 2>&1 &

in an .sh file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants