Re: [systemd-devel] Fwd: With my layer, Systemd not invoking my application at startup

2015-07-02 Thread Colin Guthrie
Hi, First of all, please keep the list included in your replies. Other people may be able to help. Vipin Nair wrote on 02/07/15 08:05: Thanks a lot Colin for your valuable inputs. here is my service unit file : + [Unit]

Re: [systemd-devel] Stricter handling of failing mounts during boot under systemd - crap idea !

2015-07-02 Thread Karel Zak
On Mon, Jun 29, 2015 at 11:24:17PM +0200, Lennart Poettering wrote: Also, again, nofail predates systemd: you should have used it for your usecase even in sysvinit. If you so will, then the old setup was already borked for you, even though admittedly the effect was less fatal. Note that

Re: [systemd-devel] How to keep certain services or mounts active during shutdown?

2015-07-02 Thread Mantas Mikulėnas
On Thu, Jul 2, 2015 at 1:24 PM, Frank Steiner fsteiner-ma...@bio.ifi.lmu.de wrote: Hi, for our diskless clients I setup the network and the root fs in the kernel/initrd and do two additional mounts in the initrd which are specific for every client. I understand the boot concept with its

[systemd-devel] How to keep certain services or mounts active during shutdown?

2015-07-02 Thread Frank Steiner
Hi, for our diskless clients I setup the network and the root fs in the kernel/initrd and do two additional mounts in the initrd which are specific for every client. I understand the boot concept with its dependencies and ordering but I've no idea how to influence the shutdown process in two

[systemd-devel] amavis

2015-07-02 Thread François Vocel
Hello, I installed Kolab on CentOS 7. The amavis service will not start. [root@kolab ~]# service amavisd restart Redirecting to /bin/systemctl restart amavisd.service Job for amavisd.service failed. See 'systemctl status amavisd.service' and 'journalctl -xn' for details. [root@kolab ~]#

Re: [systemd-devel] How to keep certain services or mounts active during shutdown?

2015-07-02 Thread Frank Steiner
Mantas Mikulėnas wrote If the 'main' network.service doesn't do anything anyway (since the network is already up), you can replace it entirely with Type=oneshot, ExecStart=/bin/true, RemainAfterExit=yes, essentially a service that does nothing at all (but still satisfies dependencies). Ok,

Re: [systemd-devel] How do I find out why a service was started? (systemd-tmpfiles-setup failed in container)

2015-07-02 Thread Colin Guthrie
Johannes Ernst wrote on 02/07/15 00:20: On Jul 1, 2015, at 14:59, Michael Biebl mbi...@gmail.com mailto:mbi...@gmail.com wrote: 2015-07-01 22:50 GMT+02:00 Johannes Ernst johannes.er...@gmail.com mailto:johannes.er...@gmail.com: Hey Martin, thanks, but: My container is degraded because

Re: [systemd-devel] changed property value in signal

2015-07-02 Thread Pradeepa Kumar
2nd try On Jul 2, 2015 10:18 AM, Pradeepa Kumar cdprade...@gmail.com wrote: hi I am new to systemd. I am using systemd 208, libdbus-1-3_1.4.18-1ubuntu1.4_i386.deb I am to monitor unit stop/failure in my application . So I am subscribing to propertiesChanged signal and paring SubState. The

Re: [systemd-devel] amavis

2015-07-02 Thread Jóhann B . Guðmundsson
On 07/02/2015 02:04 PM, François Vocel wrote: Hello, I installed Kolab on CentOS 7. The amavis service will not start. There already is a bug report about this [1] but most common cause for amavisd not starting is the configuration files is misconfigured

Re: [systemd-devel] amavis

2015-07-02 Thread Tomasz Torcz
On Thu, Jul 02, 2015 at 02:04:08PM +, François Vocel wrote: Process: 29174 ExecStart=/usr/sbin/amavisd -c /etc/amavisd/amavisd.conf (code=exited, status=227/NO_NEW_PRIVILEGES) prctl(PR_SET_NO_NEW_PRIVS, 1, 0, 0, 0) is failing. I don't now why. -- Tomasz .. oo o. oo o. .o .o o.

Re: [systemd-devel] amavis

2015-07-02 Thread Daniel Mack
On 07/02/2015 10:30 AM, Tomasz Torcz wrote: On Thu, Jul 02, 2015 at 02:04:08PM +, François Vocel wrote: Process: 29174 ExecStart=/usr/sbin/amavisd -c /etc/amavisd/amavisd.conf (code=exited, status=227/NO_NEW_PRIVILEGES) prctl(PR_SET_NO_NEW_PRIVS, 1, 0, 0, 0) is failing. I don't now

[systemd-devel] 3.7s for systemd-logind.service starting

2015-07-02 Thread RayBloodworth
Hi, everyone I'm optimizing booting performance of my system. systemd version: 208 platform: freescale i.MX6D Cortex-A9 I found systemd-logind.service takes about 3.7s for starting. Then I added many logs about system time and found that method manager_connect_bus() in