#Gentoo xscreensaver daemon how to#

In order to get syslog-ng to work well under supervise-daemon it needs to run in the foreground though. Syslog-ng calls this process mode 'safe-background'. If and when 'supervise syslog-ng' detects that it's worker process (PID 7802) has terminated it will restart it. rename the process (PID 7800) to 'supervise syslog-ng', in the parent process, and supervise its child (PID 7802).fork again to create the worker process (PID 7802) as it's child process.fork, to become a background daemon process (PID 7800) and get it to be adopted by the init process (PID 1).Syslog-ng appears to be supervising itself. The existing service is written to easily switch supervisors. It can be run as a service under supervision by editing /etc/conf.d/fancontrol: change command_args='-p $ 'įancontrol is a bash script provided by sys-apps/lm-sensors to control the fan speed.supervise-daemon needs a pidfile for itself. remove any pidfile reference that the command would create.always add supervisor='supervise-daemon'.The general recipe to bring a service under the control of supervise-daemon is to adapt its init file in /etc/init.d as follows:

#Gentoo xscreensaver daemon how to#

This article aims to provide help how to bring services under its supervision.Ĭurrently, standard Gentoo init files do not use process supervision with supervise-daemon yet: it is left to users to make these modifications to the init files.

Any terminal output sent by the daemon process to stdout and stderr can be caught by the supervisor, and then sent to the system logger or to a file.

If and when a daemon process dies (crashes) then its supervisor will notice it and try to restart it.

Supervising daemon process has a few major advantages: Pidfiles are not needed because the supervisor process remembers the pid. Backgrounding the daemon is therefore not needed, and not desired. Supervising on the other hand usually keeps the started daemon as a child process of the supervisor. When the time comes to stop, kill, or signal the daemon process s-s-d will use the saved PID file to find the right process. When s-s-d starts a process it saves the process' PID somewhere on permanent storage (typically under /run/), and backgrounds (daemonizes) the process it started. OpenRC traditionally uses start-stop-daemon, often abbreviated to s-s-d for starting and stopping programs.

4 Services which won't run under a supervisor.

It just started without any effort on my part. xinitrc file before(which I will start doing, as it seems nessasary). I know I never had to add anything to my. The first kills any xscreensaver process already running to keep from adding one each time X restarts. xinitrc file, I never had to do this in the past? Do I need to add the command xscreensaver to my.

I have to run xscreensave-demo, then it asks if I want to start the xscreensaver daemon. Now I need to start it manually everytime I restart my computer(restart x). Posted: Thu 4:49 am Post subject: xscreensaver daemon?Īs far as I remember in past installations of gentoo I did not have to do any thing special to have xscreensaver automatically start along with startx. Gentoo Forums Forum Index Desktop Environments Gentoo Forums :: View topic - xscreensaver daemon?