Re: [systemd-devel] systemd-journald error

2016-11-25 Thread Joel
Lennart - Thank you for the reply. It's not clear whether you are instructing me to do something (restart journald or rebuild initrd) or asking a question. Please note that while I have some experience with Linux and the SuSE distro (about 11 years or so), this is the first time I am

Re: [systemd-devel] systemd-journald error

2016-11-25 Thread Lennart Poettering
On Fri, 25.11.16 05:33, Joel Miller (jm-hotm...@hotmail.com) wrote: > Because I had misspelled the word "persistent" as "persisten" (dropping the > final "t"), I received the following error: > > [1.485872] systemd-journald[104]: [/etc/systemd/journald.conf:11] Failed > to parse storage

Re: [systemd-devel] after=local-fs not enforced

2016-11-25 Thread Andrei Borzenkov
25.11.2016 18:13, Benoit SCHMID пишет: > Hello, > > On 11/25/2016 04:47 AM, Andrei Borzenkov wrote: >> Yes, this is the command that tries to unmount filesystems on LVM2 >> devices, thus bypassing systemd normal dependencies. The idea of such >> service is very questionable, but it is probably

Re: [systemd-devel] after=local-fs not enforced

2016-11-25 Thread Lennart Poettering
On Thu, 24.11.16 16:20, Benoit SCHMID (benoit.sch...@unige.ch) wrote: > Hello, > > We have defined the following sap_XXX.service. > It contains the following in [Unit]: > ### > After=local-fs.target network-online.target ora_lsnr_XXX.service > remote-fs.target > Wants=ora_lsnr_XXX.service > ###

Re: [systemd-devel] Multiple notifications using sd_notify

2016-11-25 Thread Lennart Poettering
On Fri, 25.11.16 20:45, Raghavendra. H. R (raghuh...@gmail.com) wrote: > Hi All, > > Can we use sd_notify multiple times in any application to which can be used > as notification for other processes. > > If Process B & C both depends & need notification from Process A. > Can we use sd_notify in

[systemd-devel] Multiple notifications using sd_notify

2016-11-25 Thread Raghavendra. H. R
Hi All, Can we use sd_notify multiple times in any application to which can be used as notification for other processes. If Process B & C both depends & need notification from Process A. Can we use sd_notify in Process A multiple times which can be used other processes at different times ? --

Re: [systemd-devel] after=local-fs not enforced

2016-11-25 Thread Benoit SCHMID
Hello, On 11/25/2016 04:47 AM, Andrei Borzenkov wrote: > Yes, this is the command that tries to unmount filesystems on LVM2 > devices, thus bypassing systemd normal dependencies. The idea of such > service is very questionable, but it is probably not something you can > really change. > > You can

Re: [systemd-devel] WorkingDirectory=~ not interpreted by systemd

2016-11-25 Thread Lennart Poettering
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 >

Re: [systemd-devel] WorkingDirectory=~ not interpreted by systemd

2016-11-25 Thread Michael Chapman
[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] WorkingDirectory=~ not interpreted by systemd

2016-11-25 Thread Benoit SCHMID
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

[systemd-devel] systemd-journald error

2016-11-25 Thread Joel Miller
Because I had misspelled the word "persistent" as "persisten" (dropping the final "t"), I received the following error: [1.485872] systemd-journald[104]: [/etc/systemd/journald.conf:11] Failed to parse storage setting, ignoring: persisten Despite correcting the .conf file