From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Run a custom script after USB mount
Date: Tue, 28 Apr 2015 20:51:21 +0200 [thread overview]
Message-ID: <553FD6A9.5060804@mind.be> (raw)
In-Reply-To: <CADKZYY+U0L0jd=2FU9z7u1dOk0sJE5AoSrbihmV7OEYKE7=hAg@mail.gmail.com>
On 04/24/15 01:04, Santhosh Ramani wrote:
> Hello Arnout,
>
> > /# cat /etc/udev/rules.d/99-usb-detection.rules/*
> > SUBSYSTEM=="usb", ACTION=="add", KERNEL=="sda*", RUN+="/etc/hcc/usb-detected"*
> If it's a scsi device, the subsystem is block, not usb, right?
>
>
> Yes you are correct - I removed the subsystem section and it now works properly.
> I also was not restarting (or reloading) udev rules properly and that was also
> contributing to the problem.
>
> The script I want to run copies data from the USB stick and places it at a given
> location. However, it seems that by the time the script finishes executing the
> USB is not yet mounted so nothing gets copied. How can I defer execution of the
> script until the volume is mounted, yet at the same time not block udev. I tried
> the following:
>
> usb-detected: Launcher Script
>
> /etc/hcc/update_script & exit
>
> I was hoping the second script "update" would be launched as a separate process
> and will be non-blocking. I could then add sleep command in the second script
> and delay execution. However, this doesn't seem to work. I was not able to use
> 'disown' either, since it's a bash command. Similarly I didn't have any luck
> with 'at' command either.
>
> Any thoughts on how I can defer the thread and not block udev?
Actually I don't use udev myself - I just read the documentation to answer your
question. so I really can't say.
However, can't you add something to whatever script is doing the mounting, so
you can be sure that it's mounted already?
Regards,
Arnout
>
> Thank you once again for all your replies.
> Regards
>
> Santhosh
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2015-04-28 18:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 15:21 [Buildroot] Run a custom script after USB mount Santhosh Ramani
2015-04-17 16:23 ` Lionel Orry
2015-04-17 16:37 ` Santhosh Ramani
2015-04-18 12:36 ` Thomas Petazzoni
2015-04-23 3:02 ` Santhosh Ramani
2015-04-23 3:44 ` Santhosh Ramani
2015-04-23 19:56 ` Arnout Vandecappelle
2015-04-23 23:04 ` Santhosh Ramani
2015-04-28 18:51 ` Arnout Vandecappelle [this message]
2015-04-29 3:01 ` Santhosh Ramani
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=553FD6A9.5060804@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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