From: BlinkEye <blinkeye@gmx.ch>
To: linux-hotplug@vger.kernel.org
Subject: Re: bash script not CORRECTLY working from /etc/dev.d/foo/foo.dev
Date: Sat, 26 Feb 2005 14:21:01 +0000 [thread overview]
Message-ID: <1109427661.16172.14.camel@X40.blinkeye.ch> (raw)
In-Reply-To: <1109415279.16172.8.camel@X40.blinkeye.ch>
[-- Attachment #1: Type: text/plain, Size: 1344 bytes --]
On Sat, 2005-02-26 at 12:28, Tobias Klauser wrote:
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing on usenet and in e-mail?
> A: No.
> Q: Should I include quotations after my reply?
>
> (Sorry fo stealing this, Greg)
>
> On Sat, Feb 26, 2005 at 11:54:40AM +0100, BlinkEye wrote:
> > i do read the man page. i still believe this is a bug. the script IS
> > executed, but not the hole part. (i easily verified that with playing
> > sounds in different parts of the script). i tried putting it in
> > /etc/dev.d/default - still the same behaviour. it works comletely if i
> > execute it manually. besides - i removed the ACTION commands - so it's
> > not that either.
>
> It may be an error in your script which is causing the misbehaviour.
> Perhaps you could post it here to clarify this.
>
> Cheers, Tobias
I found the bug: sudo. i used 'sudo -u username mkdir foo' within my
script to make a directory (which should be owned by the user). this
works if i execute the script by hand but it doesn't work if it gets
invoked by udev automatically. well, strange behaviour and difficult to
find.
lession learned: use chown/chmod over sudo.
thanks for the help anyway.
regards
blinkeye
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-02-26 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 10:54 bash script not CORRECTLY working from /etc/dev.d/foo/foo.dev BlinkEye
2005-02-26 11:28 ` Tobias Klauser
2005-02-26 14:21 ` BlinkEye [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=1109427661.16172.14.camel@X40.blinkeye.ch \
--to=blinkeye@gmx.ch \
--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).