-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
refactor: update debian script. #965
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
Conversation
Does this handle #210 too ? |
@strk No. |
Just fix start/stop/reload on Debian 8 using system init. |
LGTM -- I noticed it drops the redirection of stdout to |
@strk Yes, you are right. I will fix that. |
I actually like that. I mean... hiding outputs is never a good idea to me.
If it has to be directed somewhere, better direct to a logfile (which is
what the issue I linked was asking, bascially).
|
@strk Yes I know your point. I think we need create another PR to fix problem you reference. |
@strk Missing your comment. All messages already logged on
But missing some http log like below:
|
@appleboy when I first filed that issue (in Gogs) what I was after was mostly Panic messages, which were printed to stderr I think (or stdout) and so always got lost. I proposed a PR which redirected stdout/stderr to a file but was not merged because not portable. Indeed it looks like having the caller (the Debian script, in this case) doing that redirection was one simple way to obtain what I was asking for. I don't know what the current idea is. Me I'd be ok with having everything going to stdout and then delegate redirection to the wrapper, so as I see you're touching that script I wonder... is there a standard way to deal with stdout/stderr in those scripts ? Should we adopt the same way ? Just let's make sure Panic messages are not lost though, as that's really bad when your server respond with |
@strk I know your point. I will take look at it and create another after this is merged. ok? |
Thanks @appleboy ! |
Trusted LGTM |
This PR fix script on Debian 8.