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

Add verbose option to codasrv #5

Open
krichter722 opened this issue May 31, 2016 · 3 comments
Open

Add verbose option to codasrv #5

krichter722 opened this issue May 31, 2016 · 3 comments

Comments

@krichter722
Copy link
Contributor

According to man codasrv there's no option to get verbose information logged to console (useful in conjunction when running the program in foreground mode/without forking/daemonizing).

experienced with 6.9.6-2+ubuntu16.04 on Ubuntu 16.04

@jaharkes
Copy link
Member

jaharkes commented Jun 1, 2016

Well it isn't called '-verbose', but there is '-debug ' which turns up verbosity of what gets written to /vice/srv/SrvLog and /vice/srv/SrvErr. Because there is a lot of output at a high debug level, writing to the console isn't terribly useful because you can only scroll back as far as your terminal (or screen) buffer allows.

Also because we are a cooperatively threaded program, when the server blocks on writing to the console, it blocks everything. So the combination of a lot of output and an often slow ssh terminal connection affects significantly how the server behaves.

@jaharkes
Copy link
Member

jaharkes commented Jun 1, 2016

Actually it is '-d ', and the server will only daemonize itself when the debug level is set to 0. So you would get the desired keep server in the foreground effect by just running,

codasrv -d 1

So now you only have to teach systemd to read the right logfile.

@jaharkes jaharkes closed this as completed Jun 1, 2016
@krichter722
Copy link
Contributor Author

The manpage should be updated because it's neither clear how to keep codasrv from forking nor does it explain the required argument - I assume a digit between 0 and 5, but it could be another range or a string as well., so it should be explained.

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

2 participants