search for: restartsec

...] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target #OnFailure=crond-notify-email@%i.service [Service] EnvironmentFile=/etc/sysconfig/crond ExecStart=/usr/sbin/crond -n $CRONDARGS ExecReload=/bin/kill -HUP $MAINPID KillMode=process Restart=on-failure RestartSec=10s ExecStartPost=/bin/sh -c "/etc/systemd/system/test.sh" [Install] WantedBy=multi-user.target My "test.sh" is very simple: #!/bin/sh echo "CROND is restarting" | /usr/bin/mailx -s "crond failure notification" myemailaddress at mydomain As you can see, I h...

...[Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target OnFailure=crond-notify-email.service [Service] EnvironmentFile=/etc/sysconfig/crond ExecStart=/usr/sbin/crond -n $CRONDARGS ExecReload=/bin/kill -HUP $MAINPID KillMode=process Restart=on-failure RestartSec=5s [Install] WantedBy=multi-user.target * crond-notify-email.service: * [Unit] Description=crond failure email notification After=crond.service Requires=crond.service [Service] Type=oneshot ExecStart=/etc/systemd/system/mail-notification.sh * /etc/systemd/system/mail-notification...

> From: Reindl Harald > > besides that you did not provide the info "embedded system" - > when you > have systemd you also have "systemctl restart > whatever.service" and in > PHP it would be passthru('command') > > you don't know how you restart a service via CLI - seriously? I know how to do it through systemctl, but I was

...;ExitOnForwardFailure yes" -o "ServerAliveInterval 60" -N -R 40443:installserver:40443 -R 8080:installserver:8080 ExecStartPre=-/usr/bin/ssh tunnel@%i "for pid in $$(ps -u tunnel | grep sshd| cut -d' ' -f1); do kill -9 $$pid; echo kill old ssh process p Restart=always RestartSec=5s StartLimitInterval=0 [Install] WantedBy=multi-user.target }}} Unfortunately on some hosts we see this warning again and again: Mar 13 23:11:14 remotehost sshd[10938]: error: bind: Address already in use Mar 13 23:11:14 remotehost sshd[10938]: error: channel_setup_fwd_listener: cannot listen t...

...service systemd-user-sessions.service time-sync.target > #OnFailure=crond-notify-email@%i.service > > [Service] > EnvironmentFile=/etc/sysconfig/crond > ExecStart=/usr/sbin/crond -n $CRONDARGS > ExecReload=/bin/kill -HUP $MAINPID > KillMode=process > Restart=on-failure > RestartSec=10s > ExecStartPost=/bin/sh -c "/etc/systemd/system/test.sh" > > [Install] > WantedBy=multi-user.target > My "test.sh" is very simple: > #!/bin/sh > echo "CROND is restarting" | /usr/bin/mailx -s "crond failure notification" myemailaddre...

...] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target #OnFailure=crond-notify-email@%i.service [Service] EnvironmentFile=/etc/sysconfig/crond ExecStart=/usr/sbin/crond -n $CRONDARGS ExecReload=/bin/kill -HUP $MAINPID KillMode=process Restart=on-failure RestartSec=10s ExecStartPost=/bin/sh -c "/etc/systemd/system/test.sh" [Install] WantedBy=multi-user.target My "test.sh" is very simple: #!/bin/sh echo "CROND is restarting" | /usr/bin/mailx -s "crond failure notification" myemailaddress at mydomain As you can see, I h...

...ithin my own service > (written in C), without resorting to fork/exec* to call systemctl why do you need it? sounds more "i like it" systemctl is the interface in doubt "it doesn't get restarted" - because you did not tell systemd to do so mine does..... Restart=always RestartSec=1 ____________________________________ [root at srv-rhsoft:~]$ cat /etc/systemd/system/smb.service [Unit] Description=Samba SMB Daemon [Service] Type=forking LimitNOFILE=32768 ExecStart=/usr/sbin/smbd -D Restart=always RestartSec=1 Nice=19 PrivateTmp=yes PrivateDevices=yes CapabilityBoundingSet=C...

...> Requires=network-online.target network-up.service > > [Service] > Type=notify > NotifyAccess=all > LimitNOFILE=32768 > ExecStart=/usr/sbin/smbd --foreground --no-process-group > ExecReload=/usr/bin/kill -HUP $MAINPID > PermissionsStartOnly=true > Restart=always > RestartSec=1 > Nice=19 > > PrivateTmp=yes > PrivateDevices=yes > ProtectKernelTunables=yes > ProtectKernelModules=yes > ProtectControlGroups=yes > MemoryDenyWriteExecute=yes > CapabilityBoundingSet=CAP_CHOWN CAP_SETGID CAP_SETUID CAP_DAC_OVERRIDE > CAP_NET_BIND_SERVICE CAP_IPC_LO...

Hello I am using samba Version 4.11.2 compiled. To start the daemon I using /samba10/samba-4.11.2/bin/samba -s /etc/samba/smb.conf To stop correctly, what is recommended ? Actually I using kill -9 ... Regards.

Hello listmates, Somehow or other my DNS services that are part of the ndjbdns-1.06-1.el7.x86_64 package would not start properly at startup. When I then start them up using systemctl: systemctl start dnscache systemctl start tinydns they start just fine. >From the log I got the following for tinydns: Oct 24 15:01:43 ns99 tinydns[1867]: tinydns: version 1.06: starting: Oct-24 2014 15:01:43

Hi Rowland, >>> - Option 1: ( my personal choice, because this keeps thing in sight >>> ) >>> - ( Domain Member settings and/or Stand-Alone installs ) >>> - Configure smb.conf ( make sure you have configured the idmap >>> settings. ) # - You must set a DOMAIN backend configuration, see >>> below idmap config * : backend = tdb >>>

...ne-ha/ovirt-ha-broker' Jan 7 09:48:03 thor systemd[1]: ovirt-ha-broker.service: Main process exited, code=exited, status=1/FAILURE Jan 7 09:48:03 thor systemd[1]: ovirt-ha-broker.service: Failed with result 'exit-code'. Jan 7 09:48:04 thor systemd[1]: ovirt-ha-broker.service: Service RestartSec=100ms expired, scheduling restart. Jan 7 09:48:04 thor systemd[1]: ovirt-ha-broker.service: Scheduled restart job, restart counter is at 44569. Jan 7 09:48:04 thor systemd[1]: Stopped oVirt Hosted Engine High Availability Communications Broker. Jan 7 09:48:04 thor systemd[1]: Started oVirt Hoste...

On 6 Apr 2020, at 12:21, Stephen John Smoogen wrote: > On Mon, 6 Apr 2020 at 04:16, Tobias Kirchhofer <collect at shift.agency> > wrote: > >> On 5 Apr 2020, at 21:20, Tobias Kirchhofer wrote: >> >>>>>> we experience difficulties with crond behaviour sending mail >>>>>> since >>>>>> CentOS 8.1. The cron job is the

...e smbd and which we can change to avoid this. > Im now testing a bit to these orders as other temp workaround. > But without risking a not starting smbd if winbind is running. > Im testing with. > > [Unit] > PartOf= > BindsTo= > > [Service] > Restart=on-failure > RestartSec=30s > >> The problem that Louis has with installing samba, doesn't have anything >> to do with those lines. It is that smbd will not run on a standalone >> server if winbind is already running, stop winbind, make no changes >> (i.e. don't add the lines Louis sugge...

...Description=Samba SMB Daemon After=network-up.service Requires=network-online.target network-up.service [Service] Type=notify NotifyAccess=all LimitNOFILE=32768 ExecStart=/usr/sbin/smbd --foreground --no-process-group ExecReload=/usr/bin/kill -HUP $MAINPID PermissionsStartOnly=true Restart=always RestartSec=1 Nice=19 PrivateTmp=yes PrivateDevices=yes ProtectKernelTunables=yes ProtectKernelModules=yes ProtectControlGroups=yes MemoryDenyWriteExecute=yes CapabilityBoundingSet=CAP_CHOWN CAP_SETGID CAP_SETUID CAP_DAC_OVERRIDE CAP_NET_BIND_SERVICE CAP_IPC_LOCK CAP_SYS_CHROOT SystemCallFilter=@system-servi...

...c/systemd/system with [Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target sssd.service [Service] EnvironmentFile=/etc/sysconfig/crond ExecStart=/usr/sbin/crond -n $CRONDARGS ExecReload=/bin/kill -HUP $MAINPID KillMode=process Restart=on-failure RestartSec=30s [Install] WantedBy=multi-user.target # ==== would fix the race. My apologies for not being clearer. > It is a kind of race condition which takes place only in the beginning > when sssd is set. Usually crond is in this use case already running, > because it is part of (our) base...

...ation=man:sshd(8) man:sshd_config(5) After=network.target sshd-keygen.service Wants=sshd-keygen.service [Service] Type=notify PIDFile=/var/run/sshd.pid EnvironmentFile=/etc/sysconfig/sshd ExecStart=/usr/local/sbin/sshd $OPTIONS ExecReload=/bin/kill -HUP $MAINPID KillMode=process Restart=on-failure RestartSec=42s [Install] WantedBy=multi-user.target OPTIONS get's picked up from /etc/sysconfig/sshd and has "-D -4" as the options. systemctl start sshd hangs and it seems like openssh isn't notifying systemd that it's started. For awhile, it seemed like sshd wasn't writing it...

I've been trying out the Restart= option in some of my own systemd service unit files - which appears to work fine However, I notice that this option is only used in a few OS provided service unit files - and was wondering about the wisdom of adding this capability to other daemons/services? (e.g. chronyd or ntpd, crond, rpcbind, etc, etc) - not that these daemons are likely to crash and

...Scheduler > After=auditd.service systemd-user-sessions.service time-sync.target > sssd.service > > [Service] > EnvironmentFile=/etc/sysconfig/crond > ExecStart=/usr/sbin/crond -n $CRONDARGS > ExecReload=/bin/kill -HUP $MAINPID > KillMode=process > Restart=on-failure > RestartSec=30s > > [Install] > WantedBy=multi-user.target > > # ==== > > would fix the race. My apologies for not being clearer. Just wondering here, if the system crond.service file is being modified/fixed with an update by rpm package, will the custom file in /etc/systemd/system also b...

Hello, Is anyone running Dovecot on either a Fedora 20 or 21 system? I'm having an issue, on a system reboot, which I admit does not happen often, Dovecot fails to start in the systemctl list, output is status failed. The issue seems to be Dovecot can not bind to the ipv6 address. Now later if I manually log in to the box and start dovecot it works just fine no problems. I've googled and