From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug#522091: udev: unable to make hdd go standby
Date: Tue, 31 Mar 2009 18:52:00 +0000 [thread overview]
Message-ID: <ac3eb2510903311152y2f7a74b6m59e3373cd7fbbcd7@mail.gmail.com> (raw)
In-Reply-To: <20090331182553.GA32456@bongo.bofh.it>
> From: John van der Kamp <john@kirika.demon.nl>
>
> Normally, I set a harddisk to standby using hdparm (hdparm -y /dev/sda)
> on startup (rc.local), but udev immediately spins the harddisk backup.
> Only after stopping udev would the harddisk stay in standby mode. I had
> no problems with udev 0.125 with this sofar. Since I have 0.140 this
> problem arose.
On Tue, Mar 31, 2009 at 20:25, Marco d'Itri <md@linux.it> wrote:
> Indeed a change event is generated when I run hdparm -y /dev/sda.
> Does anybody know why, and a workaround?
Because hdparm opens the device writable, while it should probably
only do it with O_RDONLY. Recent udev versions check the device again,
when it was opened for writing.
Kay
prev parent reply other threads:[~2009-03-31 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 18:25 Bug#522091: udev: unable to make hdd go standby Marco d'Itri
2009-03-31 18:52 ` Kay Sievers [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=ac3eb2510903311152y2f7a74b6m59e3373cd7fbbcd7@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--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).