Re: [systemd-devel] WorkingDirectory=~ not interpreted by systemd
On Fri, 25.11.16 11:40, Benoit SCHMID (benoit.sch...@unige.ch) wrote: > Good morning, > > I have set the following service: > [Unit] > Description=SAP XXX > After=autofs.service blk-availability.service local-fs.target > network-online.target ora_lsnr_XXX.service remote-fs.target > Wants=ora_lsnr_XXX.service > > [Service] > EnvironmentFile=/etc/default/sap_XXX > User=xxxadm > Group=sapsys > ExecStart=/sapmnt/XXX/exe/nuc/linuxx86_64/unige-startsap > ExecStop=/sapmnt/XXX/exe/nuc/linuxx86_64/unige-stopsap > Restart=no > TimeoutStopSec=5min > TimeoutStartSec=5min > Type=forking > WorkingDirectory=/home/xxxadm > > [Install] > WantedBy=multi-user.target > > It works fine. > If I run systemctl show, it show WorkingDirectory=/home/basadm. > > If I set : > WorkingDirectory=~ > it does not work any more because the process runs in a wrong directory. > If I run systemctl show, it does not show the "WorkingDirectory=" line. > > What am I doing wrong, when I set WorkingDirectory=~ ? > > Thanks in advance for your answers. > > PS: # systemctl --version -> systemd 219 IIRC that old systemd version doesn't support this syntax yet. Lennart -- Lennart Poettering, Red Hat ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] WorkingDirectory=~ not interpreted by systemd
[Accidentally replied off-list: resending here.] On Fri, 25 Nov 2016, Benoit SCHMID wrote: What am I doing wrong, when I set WorkingDirectory=~ ? Thanks in advance for your answers. PS: # systemctl --version -> systemd 219 Support for WorkingDirectory=~ was added in systemd v227. - Michael ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] WorkingDirectory=~ not interpreted by systemd
Good morning, I have set the following service: [Unit] Description=SAP XXX After=autofs.service blk-availability.service local-fs.target network-online.target ora_lsnr_XXX.service remote-fs.target Wants=ora_lsnr_XXX.service [Service] EnvironmentFile=/etc/default/sap_XXX User=xxxadm Group=sapsys ExecStart=/sapmnt/XXX/exe/nuc/linuxx86_64/unige-startsap ExecStop=/sapmnt/XXX/exe/nuc/linuxx86_64/unige-stopsap Restart=no TimeoutStopSec=5min TimeoutStartSec=5min Type=forking WorkingDirectory=/home/xxxadm [Install] WantedBy=multi-user.target It works fine. If I run systemctl show, it show WorkingDirectory=/home/basadm. If I set : WorkingDirectory=~ it does not work any more because the process runs in a wrong directory. If I run systemctl show, it does not show the "WorkingDirectory=" line. What am I doing wrong, when I set WorkingDirectory=~ ? Thanks in advance for your answers. PS: # systemctl --version -> systemd 219 -- _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ Benoit Schmid Tel: (+41-22) 379-7209 University of Geneva - Information Technology Division _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel