From: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
To: linux-hotplug@vger.kernel.org
Subject: Re: device symlinks being removed
Date: Mon, 18 Aug 2014 14:42:29 +0000 [thread overview]
Message-ID: <20140818144229.GD29977@in.waw.pl> (raw)
In-Reply-To: <53EE9BCD.5090101@stormcloud9.net>
On Fri, Aug 15, 2014 at 11:07:05PM -0400, Patrick Hemmer wrote:
> > My udev rule looks like this:
> >
> > SUBSYSTEM="block", SUBSYSTEMS="xen", ATTR{capability}="*",
> > ACTION="add", PROGRAM="/ec2disks -A %k", SYMLINK+="%c"
> Finally figured out it. For some reason, another event was sometimes
> being triggered on the device. My udev rule was matching only 'add'
> events, and this other event was apparently something else. So my rule
> wouldn't match, and the device would lose the symlinks.
>
> Just removed the ACTION="add" from the udev rule and all appears well.
Yep. For a similar case see http://cgit.freedesktop.org/systemd/systemd/commit/?idàd856dd48.
Zbyszek
prev parent reply other threads:[~2014-08-18 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 23:46 device symlinks being removed Patrick Hemmer
2014-08-16 3:07 ` Patrick Hemmer
2014-08-18 14:42 ` Zbigniew Jędrzejewski-Szmek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140818144229.GD29977@in.waw.pl \
--to=zbyszek@in.waw.pl \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).