See also for more information about using the per-user systemd instance. No root privilege / modification of system files needed, no cron jobs needed, nothing to install, flexible as hell (see all the related service options in the documentation).
To run it as a user, simply place a file like the following into ~/.config/systemd/user/rvice: You might want to pipe this command through a grep command to restrict the list to those processes most likely to be the one. I have found this script extremely helpful, and believe it could be very helpful even if eDirectory is not crashing regularly. Futhermore, you can plug in an email address to receive notifications. To show all the processes running or stopped but not those killed on your system, type the following: ps -ef. Use this script to monitor the ndsd process (eDirectory) on Novell OES2 and restart it if it fails for whatever reason. The Restart option takes one of no, on-success, on-failure, on-abnormal, on-watchdog, on-abort, or always. To restart a stopped process, you must either be the user who started the process or have root user authority. It can be setup as a system service or as a user service if it needs to be managed by, and run as, a particular user, which is more likely the case in OP's particular situation. If you are using a systemd-based distro such as Fedora and recent Ubuntu releases, you can use systemd's "Restart" capability for services.
0 kommentar(er)
