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

On Wed, 23.11.16 12:59, Bastien Nocera (had...@hadess.net) wrote: > The latter is currently [not > parsed](http://marc.info/?l=linux-iio=147981183211362=2) as of kernel > 4.9-rc5. > If there is no mount-matrix defined in the device-tree or ACPI DSDT, or > the data is incorrect, it can be

Re: [systemd-devel] Script in /usr/lib/systemd/system-shutdown not executed on init 6

On Wed, 23.11.16 13:42, Benoit SCHMID (benoit.sch...@unige.ch) wrote: > Hello, > > On 11/23/2016 11:55 AM, Lennart Poettering wrote: > > The scripts dropped there are executed very late during the shutdown > > process at a time where all processes have already been killed and all > > mount

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

23.11.2016 11:08, Benoit SCHMID пишет: > Hello, > > On 11/22/2016 11:46 AM, Holger Kiehl wrote: >> But users do test things under their login environment and expect them >> to run in this environment. So for some applications this is a must. > I fully agree with you. > > I am a SAP admin. > >

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

22.11.2016 12:34, Benoit SCHMID пишет: > 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. > >

Re: [systemd-devel] Script in /usr/lib/systemd/system-shutdown not executed on init 6

Am 23.11.2016 um 15:19 schrieb Benoit SCHMID: On 11/23/2016 03:03 PM, Reindl Harald wrote: than you need only to adjust "DefaultTimeoutStopSec" to ensure it does not get killed and order services proper In most of my tests, this is set to 5min. Therefore the problem is not located on the

Re: [systemd-devel] Script in /usr/lib/systemd/system-shutdown not executed on init 6

Hello, On 11/23/2016 03:03 PM, Reindl Harald wrote: > than you need only to adjust "DefaultTimeoutStopSec" to ensure it does > not get killed and order services proper In most of my tests, this is set to 5min. Therefore the problem is not located on the fact that the stop command ends too

Re: [systemd-devel] Script in /usr/lib/systemd/system-shutdown not executed on init 6

Am 23.11.2016 um 13:42 schrieb Benoit SCHMID: Is there an easy way to create a systemd service that would be stopped very early at the shutdown and would avoid the other services stop command to be executed. In other world, on my XXX server, the most important service is XXX. Stopping XXX

Re: [systemd-devel] Script in /usr/lib/systemd/system-shutdown not executed on init 6

On Wed, Nov 23, 2016 at 3:42 PM, Benoit SCHMID wrote: > Hello, > > On 11/23/2016 11:55 AM, Lennart Poettering wrote: >> The scripts dropped there are executed very late during the shutdown >> process at a time where all processes have already been killed and all >> mount

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

Hi, >> But this has not the expected impact. We were wishing with the >> "After=user.slice", that the stop sapRunning will occur before any user >> commands are stopped. >> >> Does using "After=user.slice" propagate also on all the >> *children*. That way we could ensure that our stop services'

Re: [systemd-devel] Script in /usr/lib/systemd/system-shutdown not executed on init 6

Hello, On 11/23/2016 11:55 AM, Lennart Poettering wrote: > The scripts dropped there are executed very late during the shutdown > process at a time where all processes have already been killed and all > mount points have been unmounted or at least remounted > read-only. Is there an easy way to

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

On Wed, 2016-11-23 at 12:59 +0100, Bastien Nocera wrote: > > If you want to give a try to sending a patch with a new "70- > accelerometer.hwdb" file, something along the lines of: Make that "70-sensors.hwdb" as I think we might add a few more things related to sensors in the future.

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

On Tue, 2016-11-22 at 23:43 +0100, Thomas H.P. Andersen wrote: > > > 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: > > > > > > >

Re: [systemd-devel] Script in /usr/lib/systemd/system-shutdown not executed on init 6

On Wed, 23.11.16 08:18, Benoit SCHMID (benoit.sch...@unige.ch) wrote: > Hello, > > I have added a simple script in /usr/lib/systemd/system-shutdown. > The scripts echo a message (on stdout) and create a file in /var/tmp. > I manually tested the script before rebooting to ensure that it > works

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

I am 100% sure it is run as root. Is there other debug info I can provide? Thanks for your help. 2016-11-23 16:33 GMT+08:00 陳耘志 : > The following commands are run with root privilege. > > 2016-11-22 23:52 GMT+08:00 Yun-Chih Chen : >> I've explicitly

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

On Wed, 23.11.16 18:50, Yunchih Chen (yunchih@gmail.com) wrote: > I am 100% sure it is run as root. > Is there other debug info I can provide? Thanks for your help. Just run your journalctl commands as root again? The "id" command lets you know your user identity... Lennart -- Lennart

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

On Wed, 23.11.16 09:14, Cédric BRINER (cedric.bri...@unige.ch) wrote: > Hi, > > For the context, we are trying to stop a daemon launched by a user... > > >> Hi, > >> > >> sapRunning service contains a "After=user.slice". But at the shutdown, a > >> process (write-sysv-test.pl) running in

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

On Wed, 23.11.16 16:33, 陳耘志 (yunchih@gmail.com) wrote: > The following commands are run with root privilege. Are you sure? Shells usually indicate that by using "#" as the shell prompt, instead of "$". And your command lines use the latter... > > $ journalctl -b -1 -k > > -- No entries --

Re: [systemd-devel] Shutdown/reboot problem: root hd powered off too early?

On Wed, 23.11.16 11:01, Johannes Maibaum (jmaib...@gmail.com) wrote: > ata2: exception Emask 0x10 SAct 0x0 SErr 0x199 action 0xe > frozenbd204ed5c > ata2: irq_stat 0x0040, PHY RDY changed > ata2: SError: { PHYRdyChg 10B8B Dispar LinkSeq TrStaTrns } This looks like a kernel problem.

[systemd-devel] Shutdown/reboot problem: root hd powered off too early?

Hi, I have a question concerning the shutdown/reboot phase that might be a problem with the kernel, but I was told in the Arch Linux forums to ask here too, as I have also problems with correctly logging the relevant information. I try to be as specific as I can, but I have to apologize in

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

The following commands are run with root privilege. 2016-11-22 23:52 GMT+08:00 Yun-Chih Chen : > 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.

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

Hello, On 11/22/2016 11:46 AM, Holger Kiehl wrote: > But users do test things under their login environment and expect them > to run in this environment. So for some applications this is a must. I fully agree with you. I am a SAP admin. As far as SAP is concerned, to manage the service, the

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

Hi, For the context, we are trying to stop a daemon launched by a user... >> 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. > > Slices are a concept