Thanks for the udev pointers everone - had a hectic work week with an
even more crazy one coming up, but I'll see if I can't sneak in some
time over the week for a first jab at it.
Will let post back how it goes
Regards,
Kim Pedersen
dan wrote:
yes, UDEV can do an action for a device
yes, UDEV can do an action for a device by UUID or serial number or label
etc etc.
On Wed, Oct 8, 2008 at 11:42 AM, Nils Breunese (Lemonbit) <[EMAIL PROTECTED]
> wrote:
> Rob Owens wrote:
>
> > dan wrote:
> >> Your best bet here is to use udev rule for the device
> >>
> >
> > Careful! This will
Rob Owens wrote:
> dan wrote:
>> Your best bet here is to use udev rule for the device
>>
>
> Careful! This will sync *any* drive that you plug in, won't it? Or
> is
> there a way to have a udev rule that applies to only a drive with a
> specific UUID?
I believe it's possible to have udev rul
dan wrote:
> Your best bet here is to use udev rule for the device
>
Careful! This will sync *any* drive that you plug in, won't it? Or is
there a way to have a udev rule that applies to only a drive with a
specific UUID?
-Rob
> whenever the drive gets plugged in it should run the script
>
Your best bet here is to use udev rule for the device
whenever the drive gets plugged in it should run the script
[SCRIPT1]
add the device to the array so it can sync.
launch a script in the background that watches the sync and when it is 100%
complete, remove the disk from the array. (use while
Hi everyone,
I have been following the discussions about using Linux md raid1 as a
way of creating an offline copy of the pool filesystem, which method Les
Mikesell seems to be a big proponent of.
I am about to try it out myself on an installation, where users will
connect an external harddri