Re: [systemd-devel] Promoting a pull request

On Tue, Nov 22, 2016 at 12:02:41PM +0100, Jouke Witteveen wrote: > On Tue, Nov 22, 2016 at 11:55 AM, Martin Pitt wrote: > > Jouke Witteveen [2016-11-22 11:44 +0100]: > >> I see no way of (trying to) removing the reviewed/needs-rework label > >> in the PR interface. > > > >

Re: [systemd-devel] Promoting a pull request

On Tue, Nov 22, 2016 at 01:07:51PM +0100, Lennart Poettering wrote: > On Tue, 22.11.16 11:44, Jouke Witteveen (j.wittev...@gmail.com) wrote: > > > The contribution guidelines [1] state: > > > > > After you have pushed a new version, try to remove the > > > reviewed/needs-rework label. Also add a

Re: [systemd-devel] Started process not attach to its related service.

Hello, On 11/22/2016 10:58 AM, Jonathan de Boyne Pollard wrote: > > It's now 2016, and the first rule for migrating to systemd applies > even to Oracle softwares. > > * http://jdebp.eu./FGA/systemd-house-of-horror/daemonize.html#first-rule > > *

Re: [systemd-devel] systemd-sysv-generator bug ?

On Tue, Nov 22, 2016 at 10:38 AM, Cédric BRINER wrote: > Hi, > > We have been through a lot of tests, trying to make it reproductible > with some easy scripts. You'll see at the bottom of this email, some > links on the scripts used, what we have typed in our console, and

Re: [systemd-devel] systemd-sysv-generator bug ?

Hello, On 11/22/2016 09:15 AM, Andrei Borzenkov wrote: > Mount units are also propagated to systemd user instance. So you > probably can also run this unit in systemd user context and have usual > dependencies on filesystems (like RequiresMountsFor) - at least, I > think so :) You will need to

Re: [systemd-devel] systemd-sysv-generator bug ?

On Tue, Nov 22, 2016 at 12:21 PM, Benoit SCHMID wrote: > Hello, > > On 11/22/2016 09:15 AM, Andrei Borzenkov wrote: >> Mount units are also propagated to systemd user instance. So you >> probably can also run this unit in systemd user context and have usual >> dependencies

[systemd-devel] Semantics of struct Manager.mdns_support in systemd-resolved

Hi! What's the plan for the struct Manager.mdns_support field in systemd- resolved? Currently it's set to RESOVE_SUPPORT_NO always and never gets updated regardless of the MulticastDNS= settings for network links? Still it's checked in the function manager_mdns_start() of resolve/resolved-mdns.c

[systemd-devel] accelerometer mount-matrix quirks

Hey, I'm adding support for reading the mount-matrix[1] from accelerometer devices in iio-sensor-proxy, but we'll need to add a way to override the mount-matrix in case the data from the device-tree is incorrect, or missing[2]. I was wondering whether we should ship the hwdb quirks in systemd or

Re: [systemd-devel] Promoting a pull request

On Tue, 22.11.16 11:44, Jouke Witteveen (j.wittev...@gmail.com) wrote: > The contribution guidelines [1] state: > > > After you have pushed a new version, try to remove the > > reviewed/needs-rework label. Also add a comment about the new version > > (no notification is sent just for the

Re: [systemd-devel] Started process not attach to its related service.

On Tue, 22.11.16 09:39, Benoit SCHMID (benoit.sch...@unige.ch) wrote: > Good morning, > > This topic is related to the systemd-sysv-generator thread submited by > my colleague. > I post it with another subject becaus I prefer to create another thread > as it would make too many different

Re: [systemd-devel] Started process not attach to its related service.

On Tue, Nov 22, 2016 at 11:39 AM, Benoit SCHMID wrote: ... > 2. This service starts /etc/rc.d/init.d/sap start. > % cat /etc/rc.d/init.d/sap > #!/bin/bash > ... > case "$1" in > start) > # Oracle listener and instance startup > echo -n "Starting Oracle

Re: [systemd-devel] systemd-sysv-generator bug ?

Hello, On 11/22/2016 10:25 AM, Andrei Borzenkov wrote: > I do not think so, unless you have explicit dependencies on mount > points (they are commented out in your link). If you do have explicit > dependencies, I expect this to work too. Even, when the line is uncommented, the umounts are

Re: [systemd-devel] systemd-sysv-generator bug ?

Hello, On 11/22/2016 09:15 AM, Andrei Borzenkov wrote: > Assuming that your command survives normal session exit - does adding > "After=user.slice" to your service helps? This should ensure your > service is stopped before any user processes. With "After=system.slice local-fs.target

Re: [systemd-devel] Started process not attach to its related service.

So, uh, that sounded like you value updating one file less (and even mixing user and daemon configs) above having the service actually work? Not that it's an excuse anyway. Systemd units have EnvironmentFile= for importing environment variables. Even init.d scripts can use `source` with the same

Re: [systemd-devel] Started process not attach to its related service.

On Tue, 22 Nov 2016, Mantas Mikulėnas wrote: > So, uh, that sounded like you value updating one file less (and even mixing > user and daemon configs) above having the service actually work? > But users do test things under their login environment and expect them to run in this environment. So for

[systemd-devel] Promoting a pull request

The contribution guidelines [1] state: > After you have pushed a new version, try to remove the > reviewed/needs-rework label. Also add a comment about the new version > (no notification is sent just for the commits, so it's easy to miss the > update without an explicit comment). I see no way of

Re: [systemd-devel] Promoting a pull request

Hello Jouke, Jouke Witteveen [2016-11-22 11:44 +0100]: > I see no way of (trying to) removing the reviewed/needs-rework label > in the PR interface. I click on the cog next to "Labels" on the right, there I can "untick" labels. I've done so for #4259. So maybe it's just UI obfuscation, but

Re: [systemd-devel] Started process not attach to its related service.

Hello, I have tried with "User=oracle","Environment=ORACLE_HOME=/oracle/XXX/12102" and removing the "su -". You are right. Now I have: # systemctl status ora_lsnr_XXX.service ● ora_lsnr_XXX.service - Oracle Listener XXX Loaded: loaded (/etc/systemd/system/ora_lsnr_XXX.service; disabled;

Re: [systemd-devel] Promoting a pull request

On Tue, Nov 22, 2016 at 11:55 AM, Martin Pitt wrote: > Jouke Witteveen [2016-11-22 11:44 +0100]: >> I see no way of (trying to) removing the reviewed/needs-rework label >> in the PR interface. > > I click on the cog next to "Labels" on the right, there I can "untick" >

[systemd-devel] Started process not attach to its related service.

Good morning, This topic is related to the systemd-sysv-generator thread submited by my colleague. I post it with another subject becaus I prefer to create another thread as it would make too many different questions in the same thread. 1. I have defined a service. It is started by systemd on

Re: [systemd-devel] Started process not attach to its related service.

Benoit SCHMID: echo -n "Starting Oracle Listener: " su - $ORA_OWNR -c "env ORACLE_HOME=/oracle/XXX/12102 /oracle/XXX/12102/bin/lsnrctl start LISTENER_XXX" Don't abuse su for dropping privileges. * http://jdebp.eu./FGA/dont-abuse-su-for-dropping-privileges.html It's now

Re: [systemd-devel] Started process not attach to its related service.

Hello, On 11/22/2016 10:58 AM, Jonathan de Boyne Pollard wrote: > Don't abuse su for dropping privileges. I agree that using su has drawbacks. But it also have advantages. When you upgrade your db, you upgrade the environment variables. Therefore using su allow you to centralised everything in

[systemd-devel] systemd-networkd: broken network in container

Since a few days, after some upgrades, I don't have anymore network in my container. Network is OK on my host --- Host: Archlinux - % systemctl --version systemd 231 +PAM -AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4

[systemd-devel] Missing previous boot system journal

I've explicitly enabled persistent storage in journald.conf. However, it seems that the system journal of previous boot is still missing; only some user journal persisted. Am I missing anything? Thanks in advance. I'm running on Archlinux with Linux 4.8.4 and systemd 231-4. Here's some

[systemd-devel] after=user.slice not enforced

Hi, sapRunning service contains a "After=user.slice". But at the shutdown, a process (write-sysv-test.pl) running in user.slice is killed before the end of the sapRunning's stop. # cat sapRunning.service [Unit] Description=SAP Service to ensure stopsap during shutdown After=local-fs.target

Re: [systemd-devel] accelerometer mount-matrix quirks

On Tue, 2016-11-22 at 17:23 +0100, Lennart Poettering wrote: > On Tue, 22.11.16 12:13, Bastien Nocera (had...@hadess.net) wrote: > > > Hey, > > > > I'm adding support for reading the mount-matrix[1] from > > accelerometer > > devices in iio-sensor-proxy, but we'll need to add a way to > >

Re: [systemd-devel] systemd-networkd: broken network in container

On Tue, Nov 22, 2016 at 4:54 PM arnaud gaboury wrote: > Since a few days, after some upgrades, I don't have anymore network in my > container. Network is OK on my host > > --- > Host: Archlinux - > % systemctl --version > systemd 231 > +PAM

Re: [systemd-devel] Missing previous boot system journal

On Tue, 22.11.16 23:52, Yun-Chih Chen (yunchih@gmail.com) wrote: > I've explicitly enabled persistent storage in journald.conf. However, it > seems that the system journal of previous boot is still missing; only some > user journal persisted. Am I missing anything? Thanks in advance. You

Re: [systemd-devel] systemd-networkd: broken network in container

On Tue, 22.11.16 15:54, arnaud gaboury (arnaud.gabo...@gmail.com) wrote: > Since a few days, after some upgrades, I don't have anymore network in my > container. Network is OK on my host > > --- > Host: Archlinux - > % systemctl --version > systemd 231 > +PAM -AUDIT

Re: [systemd-devel] accelerometer mount-matrix quirks

On Tue, 22.11.16 12:13, Bastien Nocera (had...@hadess.net) wrote: > Hey, > > I'm adding support for reading the mount-matrix[1] from accelerometer > devices in iio-sensor-proxy, but we'll need to add a way to override > the mount-matrix in case the data from the device-tree is incorrect, or >

Re: [systemd-devel] accelerometer mount-matrix quirks

On Tue, Nov 22, 2016 at 5:26 PM, Bastien Nocera wrote: > On Tue, 2016-11-22 at 17:23 +0100, Lennart Poettering wrote: > > On Tue, 22.11.16 12:13, Bastien Nocera (had...@hadess.net) wrote: > > > > > Hey, > > > > > > I'm adding support for reading the mount-matrix[1] from > > >