similar to: Issue with "ExecStartPost" attribute in systemd daemon fail

Gesti? Servidors wrote: > > Hello, > > I'm trying to configure a daemon (I'm doing tests with "crond" daemon) to send me an email after daemon restart. My "crond.service" file is: > # /etc/systemd/system/crond.service > [Unit] > Description=Command Scheduler > After=auditd.service systemd-user-sessions.service time-sync.target >

Hellos, Yes, I did some tests with "OnFailure" attribute, but the result was the same: system didn't sent any mail. Daemon and script files were: * crond.service: * [Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target OnFailure=crond-notify-email.service [Service] EnvironmentFile=/etc/sysconfig/crond

Hello, I'm trying to configure a daemon (I'm doing tests with "crond" daemon) to send me an email after daemon restart. My "crond.service" file is: # /etc/systemd/system/crond.service [Unit] Description=Command Scheduler After=auditd.service systemd-user-sessions.service time-sync.target #OnFailure=crond-notify-email@%i.service [Service]

On Mon, 6 Apr 2020 at 06:59, Tobias Kirchhofer <collect at shift.agency> wrote: > 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

> On Mon, 6 Apr 2020 at 06:59, Tobias Kirchhofer <collect at shift.agency> > wrote: > >> 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: >> >> >>

Am 23.02.2016 um 01:30 schrieb Paul D. DeRocco: >> 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

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

I have several systems running 64bit SLES11SP1. I''m trying to Live Migrate between a couple of them and it''s not working, although the same VM will run on each one starting it manually. The system are not identical. Would one expect migration to work between these two systems? See below. Thanks, James The first system is a ProLiant DL360 G6: Proc 1:2533 MHz Execution

Reindl on the compiled version the samba binary file is not in /usr/sbin/smbd and i think start whith samba file not with smbd El lun., 21 sept. 2020 10:41, Reindl Harald <h.reindl at thelounge.net> escribi?: > > > Am 21.09.20 um 14:47 schrieb jmpatagonia via samba: > > Hello I am using samba Version 4.11.2 compiled. > > > > To start the daemon I using > >

We try to run a reliable ssh tunnel vis systemd. This is the unit configuration file: {{{ [Unit] Description=Tunnel For %i After=network.target [Service] User=autossh ExecStart=/usr/bin/ssh -o "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

Dear fellow NUT-UPS users, I'm writing this message mostly "for the record" - for others who will follow in my footsteps. Apparently, I'm not the only one, trying to find a way to "make my UPS to initiate the graceful shutdown process earlier". The topic is kind of documented in various different places, and there are a number of howto's and forum posts in the

On 17.11.2015 17:51, m.roth at 5-cent.us wrote: > Nick Bright wrote: >> On 11/17/2015 8:18 AM, James B. Byrne wrote: >>> This behaviour is congruent with SELinux. One utility adjusts the >>> permanent configuration, the one that will be applied at startup. >>> Another changes the current running environment without altering the >>> startup config. From

On 12/15/2015 11:26 AM, m.roth at 5-cent.us wrote: > Really? There's no systemd target to restart it, and graphical.target > doesn't do it? Um..... Why do you think that? # systemctl status gdm.service gdm.service - GNOME Display Manager Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled) Active: active (running) since Sun 2015-11-01 17:15:13 UTC; 1 months 13

Gordon Messmer wrote: > On 12/15/2015 11:26 AM, m.roth at 5-cent.us wrote: >> Really? There's no systemd target to restart it, and graphical.target >> doesn't do it? Um..... > > Why do you think that? Sorry, I would have thought that graphical.target would do it. And suppose I'm using kdm...? mark > > # systemctl status gdm.service > gdm.service -

I am getting startup errors for nfs ganesha CentOS 7.3 with gluster 3.10.2 from CentOS storage sig # systemctl status nfs-ganesha ? nfs-ganesha.service - NFS-Ganesha file server Loaded: loaded (/usr/lib/systemd/system/nfs-ganesha.service; disabled; vendor preset: disabled) Active: failed (Result: core-dump) since Wed 2017-06-14 14:00:49 EDT; 4s ago Docs:

I have a test environment. Three node HCI cluster. CentOS8 build. Gluster as file system with standard cockpit deploy of HCI. Converted to CentOS Streams which seemed to go fine. Did a yum update and no issues. Did a reboot.. and now engine will no longer start. So I can no longer start my Virtual machines. I posted as bug https://bugzilla.redhat.com/show_bug.cgi?id=1911910 I posted to

Hi Louis, you could use the systemd "requires=" directive to enforce, that samba/smbd is running before winbind. Hth Oliver On 27.09.2018 12:04, L.P.H. van Belle via samba wrote: > Hai, > Small comment here.. > >> Not saying you shouldn't add it and like you, I always add it if >> required, but what I was trying to point out to Louis is, you don't

Am 21.09.20 um 14:47 schrieb jmpatagonia via samba: > 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 ... SIGTERM or use a OS which a proper service manager like systemd which sends SGTERM to any process

Latest Oracle Linux (7.5) and openssh 7.4 is bundled as an rpm. this runs fine. if I download openssh 7.6 or 7.7, compile it with the flags --with-pam and --with-pid-dir=/var/run and install it to /usr/local, modify the sshd.service file to point to /usr/local/sbin/sshd, the start hangs. The sshd.service files looks like this: [Unit] Description=OpenSSH server daemon Documentation=man:sshd(8)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 17/11/15 17:29, Dennis Jacobfeuerborn wrote: > On 17.11.2015 17:51, m.roth at 5-cent.us wrote: >> Nick Bright wrote: >>> On 11/17/2015 8:18 AM, James B. Byrne wrote: >>>> This behaviour is congruent with SELinux. One utility adjusts >>>> the permanent configuration, the one that will be applied at