search for: environmentfil

...and didn't find anything looking promising. In non-systemd systems, httpd was started by a shell script (/etc/rc.d/init.d/httpd) which sourced the file /etc/sysconfig/httpd, so you could embed shell code in the file and it would be evaluated. In systemd systems, the httpd.service unit has: EnvironmentFile=/etc/sysconfig/httpd For systemd units, setting this will cause the systemd unit to read in the file for variables, but it ignores anything that isn't a simple 'foo=bar' syntax. It doesn't evaluate shell scripts. HOWEVER, the logic of your shell script is something that can be...

I'm trying to install DB2 on a CentOS 7 server. The problem I'm seeing is that the Apache httpd server fails to pick up the db2 environment variables. On an older version running under CentOS 5 this was done by inserting the following lines into the httpd start script in /etc/sysconfig/httpd: if test -f /db2home/db2inst1/sqllib/db2profile; then . /db2home/db2inst1/sqllib/db2profile fi

...e and mask smbd.service,nmbd.service, 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...

..., I see we have two files controlling memcached 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="1...

...gt;> >> 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 >> >> > > that is basically what init scripts do, i.e if fileserver start th...

...; > > > 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 /et...

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

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

.... 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 NotifyAccess=all PIDFile=/var/run/samba/smbd.pid LimitNOFILE=16384 EnvironmentFile=-/etc/default/samba ExecStart=/usr/sbin/smbd $SMBDOPTIONS ExecReload=/bin/kill -HUP $MAINPID LimitCORE=infinity [Install] WantedBy=multi-user.target Jeremy Allison via samba kirjoitti 9.1.2018 klo 21:47: > On Tue, Jan 09, 2018 at 07:57:41AM +0200, John Doe via samba wrote: >> I added on...

...Failure" 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 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.servic...

...mcat. alter as necessary. d /run/tomcat 0700 tomcat tomcat - See the systemd-tmpfiles(8) and tmpfiles.d(5) man pages. After you install that file, do systemd-tmpfiles --create The second method is to add an ExecStartPre to /usr/lib/systemd/system/tomcat.service, e.g., [Service] Type=simple EnvironmentFile=/etc/sysconfig/tomcat # this assumes that TOMCAT_USER is defined correctly # in the EnvironmentFile ExecStartPre=/usr/bin/install -d \ -o ${TOMCAT_USER} -m 0700 /run/tomcat ExecStart=/usr/libexec/tomcat/server start # etc etc If you go that route, then after editing the service file, do sy...

...est machine for a scheduled upgrade. > systemctl cat bind9 > # /lib/systemd/system/bind9.service > [Unit] > Description=BIND Domain Name Server > Documentation=man:named(8) > After=network.target > Wants=nss-lookup.target > Before=nss-lookup.target > > [Service] > EnvironmentFile=/etc/default/bind9 > ExecStart=/usr/sbin/named -f $OPTIONS > ExecReload=/usr/sbin/rndc reload > ExecStop=/usr/sbin/rndc stop > > [Install] > WantedBy=multi-user.target > > > The correct workaround is edit, and add.. > systemctl edit bind9 > Add : > [Service]...

...nfig crate the file correctly: root at vdmpp1:/srv# cat /run/sysconfig/nfs-utils PIPEFS_MOUNTPOINT=/run/rpc_pipefs RPCNFSDARGS=" 8" RPCMOUNTDARGS="--manage-gids" STATDARGS="" RPCSVCGSSDARGS="-vvvvv -n" but the nfs(s) systemd unit file misses the 'EnvironmentFile=' directive: https://www.freedesktop.org/software/systemd/man/systemd.exec.html#EnvironmentFile= Seems time to fire up a bug... -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia'' http://www.lanostrafamiglia.it/ Polo FVG -...

...it after the interface change. cat /lib/systemd/system/smbd.service [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 NotifyAccess=all PIDFile=/var/run/samba/smbd.pid LimitNOFILE=16384 EnvironmentFile=-/etc/default/samba ExecStart=/usr/sbin/smbd $SMBDOPTIONS ExecReload=/bin/kill -HUP $MAINPID LimitCORE=infinity [Install] WantedBy=multi-user.target ------------------ cat /lib/systemd/system/nmbd.service [Unit] Description=Samba NMB Daemon Documentation=man:nmbd(8) man:samba(7) man:smb.conf(5)...

On Mon, 3 Sep 2018 15:37:03 +0200 Luca Olivetti via samba <samba at lists.samba.org> wrote: > El 3/9/18 a les 15:23, Robert Marcano via samba ha escrit: > > >> > >> I run this cron job every minute. Winbind usually crashes once or > >> twice a day > >> > >> #!/bin/bash > >> getent group | grep -q 513 && exit 0 >

...ir=/var). samba-ad.service file content ------------------------------------------------------------------------------------ [Unit] Description=Samba Active Directory Services Documentation=man:samba(8) After=network.target [Service] Type=forking PIDFile=/var/run/samba/samba.pid LimitNOFILE=16384 EnvironmentFile=-/etc/default/samba ExecStartPre=-/usr/bin/mkdir /var/run/samba ExecStart=/usr/sbin/samba -D -M standard ExecReload=/usr/bin/kill -HUP $MAINPID #FailureAction= [Install] WantedBy=multi-user.target ------------------------------------------------------------------------------------ I start from...

hey folks, we are migrating our tomcat setup over to centos 7. Im converting init-scripts over to systemd services and whatnot.. One thing that Ive noticed is that my systemd startup script cant seem to write to /var/run as a non-root user to drop a pidfile.. If I create a directory in /var/run owned by my user, it gets wiped out on reboot. Ive searched and found this

...around the problem locally by re-configuring libvirtd to > run persistently rather than using socket activation: > > systemctl disable --now libvirtd{,-ro,-admin}.socket > > cat > /etc/systemd/system/libvirtd.service.d/override.conf <<EOF > [Service] > EnvironmentFile= > EOF > > systemctl restart libvirtd > > Package versions in case this helps correlate something: > > - libvirt-9.0.0-3.fc38.x86_64 > - systemd-253.5-1.fc38.x86_64 > - kernel-6.3.6-200.fc38.x86_64 > > Libvirt uri: qemu:///system > > -- > Lars Kell...

Rowland, I was thinking if I did anything wrong, but your clarification cleared my mind. I appreciate your help. I'm waiting if other person had a same issue and solved it. Thanks a lot for your help, Igor Sousa On Fri, Apr 26, 2019, 13:26 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Fri, 26 Apr 2019 13:02:07 -0300 > Igor Sousa <igorvolt at gmail.com>

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