Skip to content

Conversation

@robert-budde
Copy link

In order to use a very sleek systemd service sh.py should not fork while still being not too verbose on logging. Not forking allows systemd to monitor the process without using an additional pid-file.

@robert-budde
Copy link
Author

Marcus, any thoughts on this one?

@encbladexp
Copy link

Maybe -f could be avoided. Example:

  • -d runs sh.py in background, without verbose.
  • -v runs sh.py in foreground, with verbose.
  • -d -v runs sh.py in background, with verbose.
    Simply specifying nothing should run sh.py in foreground, without verbose mode enabled.

@robert-budde
Copy link
Author

Sure. This would be the most straightforward way of doing things. But it would break compatibility with all existing installations.
I assume that this is not going to happen, therfore I proposed a less intrusive way.

@mknx
Copy link
Owner

mknx commented Mar 29, 2015

Hi,

I will not merge changes to the base system, because I'm going to adapt the license. And if there are other contributors I cannot change it without asking them.

I'm going to send an email to the contributors/developers to discuss this topic.

Regards

Marcus

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

Successfully merging this pull request may close these issues.

3 participants