Logs Manaagement - I/0 crashes!

[ron]

Option to disable logs ??
1xxx accounts with every action getting logged into my I/O streams - i hope you understand how basic this feature is and that it is implemented ASAP

[martin@rootjazz]

Add the file

nologs.txt

to your config dir and default logging is off

from the next update

[martin@rootjazz]

https://rootjazz.com/twitterdub/updatetesting.html

[ron]

Hey,

I did add nologs to the config directory, however logging still goes on. Please fix
100% sure - tested comprehensively


Log id - 79691

[ron]

How much time more will this take. Getting really tiring

[martin@rootjazz]

https://rootjazz.com/twitterdub/updatetesting.html

How much time more will this take. Getting really tiring

Just wind it in a bit ron, seriously... :-\



Feature request,
feature added (admittedly build issue)
fixed - reuploaded

turn around was what? 3 days over the festive period, start to finish

[ron]

https://rootjazz.com/twitterdub/updatetesting.html

How much time more will this take. Getting really tiring

Just wind it in a bit ron, seriously... :-\



Feature request,
feature added (admittedly build issue)
fixed - reuploaded

turn around was what? 3 days over the festive period, start to finish

Thanks man, this issue was affecting me for a whole month but never mind, I am happy if it's fixed.
Just a lot of pressure to make money from this - have taken time out from a lot of important stuff to do this project.

[ron]

Logging is still happening for streams !

I see these messages all over the place in the logs folder. This happens in bulk when authorization fails in a matter of seconds !!
You need to fix the authorization error on this first and this could also be the cause of the disk io crashes with repeated logging of all errors.
Also why is it trying to login again so fast in streams ? Why doesn't it show as failed after 4-5 consecutive tries.
It's all fugazi

* ERROR: Could not receive information related with currently logged user.
Stream Stopped:
* ERROR: Could not receive information related with currently logged user.
Stream Stopped:
* ERROR: Could not receive information related with currently logged user.
Stream Stopped:
* ERROR: Could not receive information related with currently logged user.
Stream Stopped:
* ERROR: Could not receive information related with currently logged user.
Stream Stopped:
* ERROR: Could not receive information related with currently logged user.
Stream Stopped:
* ERROR: Could not receive information related with currently logged user.

[martin@rootjazz]

Errors are still logged, general logs are not. This is an error, thus logged.


As to why it is happening so fast, I guess connection fails bot tries again. In all my tests this will then work. Never had the situation where twitter just refuses it and it thrashes in a state of refusal try again.


Will add a pause and a max attempts then fail check

[martin@rootjazz]

done - next update