Re: [systemd-devel] Weird udev issue: char device replaced by regular file on suspend

2015-06-26 Thread Robert Milasan
On Thu, 25 Jun 2015 22:07:27 +0200 Johannes Bauer dfnsonfsdu...@gmx.de wrote: Oh, okay, this would be insanely weird then if it were a kernel bug. Do you think LKML is the right place to post this to then? No, I think the suspend-to-RAM scripts should be checked or asked on the mailing

Re: [systemd-devel] howto handle one time shutdown programs

2015-06-26 Thread Andrei Borzenkov
В Thu, 25 Jun 2015 11:09:22 -0700 Johannes Ernst johannes.er...@gmail.com пишет: Hallo Andreas, On Jun 25, 2015, at 7:57, Andreas Buschmann busch...@tech.net.de wrote: Hello, I am writing a systemd .service file to handle NVDIMMs. - start - stop - reload all work

Re: [systemd-devel] SysVInit service migration to systemd

2015-06-26 Thread Lukáš Nykrýn
Lesley Kimmel píše v Pá 26. 06. 2015 v 08:15 -0500: Hi all; I've been working with RHEL5/6 for the past several years and have developed many init scripts/services which generally use lock files and PID files to allow for tracking of the service status. We are moving to RHEL7 (systemd) in

Re: [systemd-devel] SysVInit service migration to systemd

2015-06-26 Thread Andrei Borzenkov
В Fri, 26 Jun 2015 10:02:41 -0500 Lesley Kimmel ljkimme...@hotmail.com пишет: Thanks for the information. I've seen that blog before. Unfortunately, it only describes a starting a service that already has a good level of integration with some of the underlying infrastructure of systemd (e.g.

Re: [systemd-devel] SysVInit service migration to systemd

2015-06-26 Thread Mantas Mikulėnas
On Fri, Jun 26, 2015 at 4:15 PM, Lesley Kimmel ljkimme...@hotmail.com wrote: Hi all; I've been working with RHEL5/6 for the past several years and have developed many init scripts/services which generally use lock files and PID files to allow for tracking of the service status. We are moving

Re: [systemd-devel] Weird udev issue: char device replaced by regular file on suspend

2015-06-26 Thread Johannes Bauer
On 26.06.2015 07:43, Greg KH wrote: It's one byte long and this one byte is exactly the data that my userspace program tried to send. But obviously my user space program could not have created that node (no permission to write in /dev, obviously, and my program has no suid or anything, runs

Re: [systemd-devel] Weird udev issue: char device replaced by regular file on suspend

2015-06-26 Thread Johannes Bauer
No way! You're totally awesome, that was the right track... On 26.06.2015 07:14, Martin Pitt wrote: This sounds like a script or program that runs for suspend tries to apply an atomically update file contents approach (write data into a file.new, then mv file.new file) to a /dev node, which

Re: [systemd-devel] howto handle one time shutdown programs

2015-06-26 Thread Reindl Harald
Am 26.06.2015 um 09:31 schrieb Andrei Borzenkov: How is that different from the user executing: systemctl start your.service systemctl stop your.service systemctl start your.service without reboot? Those initscripts I am aware of avoided this issue by not stopping anything on restart

[systemd-devel] SysVInit service migration to systemd

2015-06-26 Thread Lesley Kimmel
Hi all; I've been working with RHEL5/6 for the past several years and have developed many init scripts/services which generally use lock files and PID files to allow for tracking of the service status. We are moving to RHEL7 (systemd) in the near future and I am looking for instruction or

Re: [systemd-devel] howto handle one time shutdown programs

2015-06-26 Thread Colin Guthrie
Andreas Buschmann wrote on 25/06/15 15:57: Hello, I am writing a systemd .service file to handle NVDIMMs. - start - stop - reload all work The problem child is restart. Restart is internally implemented as stop followed by start. The problem is, that stop calls a program which

[systemd-devel] Failed to mount a crypted device with 'tmp' option

2015-06-26 Thread Francis Moreau
Hi, I'm setting up an encrypted device at boot using cryptsetup. This device is formatted at each boot (I'm using 'tmp' option in /etc/crypttab). Also this device is mounted at boot time (a corresponding entry in /etc/fstab has been made) and is also fsck'ed (fs_passno=2). However it seems that