Re: [systemd-devel] How to stop systemd-udevd reading a device after dd

On Thu, Oct 12, 2017 at 6:01 PM, Akira Hayakawa wrote: > And I want to stop the read request because it makes it difficult to test > kernel code. > So the second question is: how can I stop the read request? You can install local udev rule that will disable udev's monitoring of the block device

Re: [systemd-devel] How to stop systemd-udevd reading a device after dd

Hi, Thanks. The udev rule worked. But only for the unexpected read after write (or close the device by dd maybe) Because the device I want to remove udev control is device-mapper devices which have prefix dm-, I changed the KERNEL in the line from sdb* to dm* then worked. But still I have probl

[systemd-devel] Conflicts no longer working as expected during boot in v235

Hi, in Debian we enable systemd-timesyncd by default. A while ago, I decided to install chrony. The chrony.service file has Conflicts=systemd-timesyncd.service. In the past this was sufficient to ensure that only chrony is started. After the upgrade to v235 I now see this: $ systemctl status syst

Re: [systemd-devel] Conflicts no longer working as expected during boot in v235

This is 100% reproducible here, fwiw. Both services are always started after a reboot. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? ___ systemd-devel mailing list systemd-devel@lists.fre

Re: [systemd-devel] How to give users permissions to /dev/kfd

On 10/12/2017 09:04 PM, Mantas Mikulėnas wrote: > On Fri, Oct 13, 2017, 00:30 Tom Stellard > wrote: > > Hi, > > The amdkfd kernel driver exposes the /dev/kfd device file for doing gpgpu > computing on AMD GPUs, I would like to setup the permissions on this

[systemd-devel] journal: Receiving messages from the future

Hi, TL;DR: Server is receiving log message via systemd-journal-remote from 14s in the future (sender clock is 14s fast). Causes journal files to close, rotate and start anew on every message/batch. Check at journal-file.c:621 is checking for messages "from the future" from perspective of local

Re: [systemd-devel] How to stop systemd-udevd reading a device after dd

I've investigate myself what uevent are sent after each command. I use "udevadm monitor" to watch the event sent from kernel. The experiment starts from removing the existing device but if it's placed at last, the uevents are the same. What's very curious to me is that the ACTION!="remove" in my

Re: [systemd-devel] Persistent address on "Lost carrier"

On Friday 16 June 2017 01:06 PM, Lennart Poettering wrote: On Thu, 15.06.17 18:22, Amish (anon.am...@gmail.com) wrote: Hmm, that wasn't the actual question though, was it? The point was just to make networkd ignore carrier status (i.e. often there's no need to remove addresses just because the