search for: execstart

On a machine with virtual networking is enabled and two ether net controllers eth0/192.168.1.2 and eth1/192.168.1.3 and having SAMBA smb.conf set to: dns interfaces = lo br0 is there a chance for: 1) The system not to boot with DNS working 2) The DNS server bounce between eth0 and eth1 3) The DNS server portion work on boot sometimes on eth0, but when software restarted only work on eth1 or

Hai Rowland, Yes, that correct. If you use this in override.conf then its. ( so not a copy of the service file to /etc/systemd ) systemctl edit rpc-gssd.service [Service] ExecStart= ExecStart=/Your/Own/Script/script.sh Note the empty line, without that won the override is NOT working. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: Rowland Penny [mailto:rpenny at samba.org] > Verzonden: dinsdag 6 november 2018 16:32 > Aan: samba at lists.samba.org...

...t belongs to the bridge and nothing else that's an example how a proper bridge is configured and my "network-up.service" is part of "network-online.target" while evry other service has "After=network-online.target" *and* "Requires=network-online.target" ExecStart=-/usr/sbin/ip link add name br-lan type bridge ExecStart=-/usr/sbin/ip link set dev br-lan up ExecStart=-/usr/sbin/ip a add 192.168.2.2/255.255.255.0 broadcast 192.168.2.255 dev br-lan ExecStart=-/usr/sbin/ip link set dev lan-spare1 master br-lan up ExecStart=-/usr/sbin/ip link set dev lan-spare2 m...

...winbind.service. This is the samba-ad-dc.service script: [Unit] Description=Samba AD Daemon Documentation=man:samba(8) man:samba(7) man:smb.conf(5) After=network.target [Service] Type=notify NotifyAccess=all PIDFile=/run/samba.pid LimitNOFILE=16384 EnvironmentFile=-/etc/default/samba ExecStart=/usr/sbin/samba $SAMBAOPTIONS ExecReload=/bin/kill -HUP $MAINPID [Install] WantedBy=multi-user.target Am 12.07.2016 um 20:53 schrieb Sonic: > On Tue, Jul 12, 2016 at 10:09 AM, Sonic <sonicsmith at gmail.com> wrote: >> Mine use Type=forking, I had some issues with Type=notify &gt...

...lt 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 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 [Servic...

...> > cat /opt/rh/httpd24/root/etc/sysconfig/httpd > > export PATH=/opt/rh/python27/root/usr/bin:$PATH > export > LD_LIBRARY_PATH=/opt/rh/python27/root/usr/lib64${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}} I am running nginx and uWSGI. I added this to /etc/systemd/system/uwsgi.service: ExecStart=/usr/bin/scl enable python27 bash; /usr/bin/uwsgi --emperor /etc/uwsgi/sites But it did not start: Loaded: loaded (/etc/systemd/system/uwsgi.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since Mon 2017-12-11 17:20:36 EST; 6s ago Process: 24492 ExecStart=/...

...it's not possible to have the same functionality as is with init script. 1) systemd does not support: source /etc/sysconfig/ups if [ "$SERVER" = yes ]; then /sbin/upsdrvctl... /.../upsd /.../upsmon else /.../upsmon fi because it has it's special syntax. 2) it does not support: ExecStart=[ "$SERVER" != yes ] || /sbin/upsdrvctl ExecStart=[ "$SERVER" != yes ] || /.../upsd ExecStart=/.../upsmon because it does not use shell 3) it "somehow" supports ExecStart=/usr/libexec/nut/systemd_helper and put shell script code from #1 there and handle other stuff m...

...put the system in permissive mode > to see if that's the case. If so, "grep AVC /var/log/audit/audit.log" > for more info. Another random thought When I invoke from the CLI - there is a -nofork=yes as a part of the invocation. When systemd tries to do the invocation via the ExecStart line - the original clamd at .service file had this --nofork=yes also, the problem was that this just caused an abend of the start up with the message: > /usr/sbin/clamd: unrecognized option `--nofork=yes' > ERROR: Unknown option passed > ERROR: Can't parse command line option...

...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] 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&...

...service nut-server status nut-server.service - Network UPS Tools - power devices information server      Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; vendor preset: enabled)      Active: failed (Result: exit-code) since Tue 2020-08-11 22:13:42 EDT; 1min 18s ago     Process: 1537 ExecStart=/sbin/upsd (code=exited, status=1/FAILURE) Warning: some journal files were not opened due to insufficient permissions. proton at proton:~$ service nut-client status nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller      Loaded: loaded (/lib/systemd/system/n...

...ached under the new sysctl system. At least, using sysctl is new to me! I see we have this file: [root at web1:~] #cat /usr/lib/systemd/system/memcached.service [Unit] Description=Memcached Before=httpd.service After=network.target [Service] Type=simple EnvironmentFile=-/etc/sysconfig/memcached ExecStart=/usr/bin/memcached -u $USER -p $PORT -m $CACHESIZE -c $MAXCONN $OPTIONS [Install] WantedBy=multi-user.target And we have this one under sysconfig: [root at web1:~] #cat /etc/sysconfig/memcached PORT="11211" USER="memcached" MAXCONN="1024" CACHESIZE="64" OP...

I just noticed that by running by commands /usr/sbin/smbd -D or /usr/sbin/smbd -i without systemd's unit, all shares work perfectly so the problem must then be somehow related to systemd.. Let the testing continue.. I also tested what happens if I comment out everything and just use ExecStart=/usr/sbin/smbd -D as that command worked on the console. That did not help. For the record, this is the default unit-file: [Unit] Description=Samba SMB Daemon Documentation=man:smbd(8) man:samba(7) man:smb.conf(5) After=network.target nmbd.service winbind.service [Service] Type=notify NotifyAcces...

...d the "Managing the Samba AD DC Service Using Systemd" and I've created /etc/systemd/system/samba-ad-dc.service file with the following content: [Unit] Description=Samba Active Directory Domain Controller After=network.target remote-fs.target nss-lookup.target [Service] Type=forking ExecStart=/usr/local/samba/sbin/samba -D PIDFile=/usr/local/samba/var/run/samba.pid ExecReload=/bin/kill -HUP $MAINPID [Install] WantedBy=multi-user.target I've created a mask to smbd, nmbd and winbind and I've disabled them following this command: # systemctl mask smbd nmbd winbind # systemctl di...

...ion on what you are seeing and how you > have it set up? I can try to duplicate it in EPEL and/or put in bugs > on the package. > > Of course and thanks in advance Stephen. My dnscrypt startup scripts use the following options: [Service] Type=forking PIDFile=/var/run/dnscrypt-cs.pid ExecStart=/usr/sbin/dnscrypt-proxy \ --daemonize \ --user=nobody \ --pidfile=/var/run/dnscrypt-cs.pid \ --ephemeral-keys \ --resolver-name=cs-fi \ --logfile=/tmp/cs.log \ --local-address=127.0.0.1:6354 Restart=on-abort [Service] Type=forking PIDFile=/var/run/dnscrypt-ipredator.pid ExecStart=/usr/sbin...

...7) man:smb.conf(5) >> >> After=network.target >> >> [Service] >> >> Type=notify >> >> NotifyAccess=all >> >> PIDFile=/run/samba.pid >> >> LimitNOFILE=16384 >> >> EnvironmentFile=-/etc/default/samba >> >> ExecStart=/usr/sbin/samba $SAMBAOPTIONS >> >> ExecReload=/bin/kill -HUP $MAINPID >> >> [Install] >> >> WantedBy=multi-user.target >> >> > > that is basically what init scripts do, i.e if fileserver start the > nmbd, smbd and winbindd binaries, if AD D...

...iling though: # systemctl status timidity timidity.service - timidity daemon Loaded: loaded (/etc/systemd/system/timidity.service; enabled) Active: failed (Result: exit-code) since Sat ... Process: 955 ExecStop=/bin/kill -s TERM $MAINPID (code=exited, status=1/FAILURE) Process: 790 ExecStart=/usr/bin/timidity -iAD (code=exited, status=0/SUCCESS) Main PID: 790 (code=exited, status=0/SUCCESS) CGroup: /system.slice/timidity.service ...systemd[1]: Started timidity daemon. ...kill[955]: Usage: ...kill[955]: kill [options] <pid|name> [...] (standard help message ommited) ....

...); # systemctl -l status vncserver@:3.service ? vncserver@:3.service - Remote desktop service (VNC) Loaded: loaded (/etc/systemd/system/vncserver at .service; enabled; vendor preset: disabled) Active: failed (Result: resources) since Fri 2017-07-28 13:31:15 EDT; 54s ago Process: 19173 ExecStart=/usr/sbin/runuser -l root -c /usr/bin/vncserver %i (code=exited, status=0/SUCCESS) Process: 19170 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS) Jul 28 13:31:12 homebase.home.htt systemd[1]: Starting Remote desktop service...

...greenstone3.service # Systemd unit file for Greenstone 3 [Unit] Description=Greenstone 3 Server After=syslog.target network.target [Service] Type=forking PIDFile=/run/greenstone3/greenstone3.pid Environment=PATH=/usr/apache-ant-1.9.6/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin ExecStart=/usr/bin/bash -c "cd /greenstone/gs3/ && ant start ; /usr/sbin/pidof java | awk '{print $1}' > /run/greenstone3/greenstone3.pid" SuccessExitStatus=143 User=gs3 Group=gs3 [Install] WantedBy=multi-user.target Thanks

...nvironment is systemd. I'm maintaining the ipset package in Fedora, and it would be nice to provide users a way to have their ipsets automatically restored at boot time, and saved at shutdown. In systemd, a unit file provides a command line to run in order to start or stop the service with the ExecStart and ExecStop directives. However, there's no input/output redirection available in systemd, so I can't use: ExecStart=/usr/bin/ipset restore < /etc/ipset/ipset.save ExecStop=/usr/bin/ipset save > /etc/ipset/ipset.save One solution is to use instead: ExecStart=/bin/sh -c...

...> > [root at web1:~] #cat /usr/lib/systemd/system/memcached.service > > [Unit] > > Description=Memcached > > Before=httpd.service > > After=network.target > > > > [Service] > > Type=simple > > EnvironmentFile=-/etc/sysconfig/memcached > > ExecStart=/usr/bin/memcached -u $USER -p $PORT -m $CACHESIZE -c $MAXCONN > > $OPTIONS > > > > [Install] > > WantedBy=multi-user.target > > > > And we have this one under sysconfig: > > > > [root at web1:~] #cat /etc/sysconfig/memcached > > PORT="1121...