thank you Seth,
I have no problems with the script executed at the UDEV event (if this is the meaning you attribute to the term <UDEV script>).
I've already done this script that works, if run from a terminal.If by the term <UDEV script> you mean something different, please tell me.
The problem is that this script is not executed as a result of the UDEV event.
- - - - - -But maybe there is still something not clear for me that I can ask you:
The HD (USB) that I am using, is divided into three partitions (in order to keep the saved data separate):
= - = - = - = - = - =
the blkid command give this output ...:
/ dev / sdc1: LABEL = "PRTZm_sys-admin" UUID = "1A5CEE7149E4BA81" TYPE = "ntfs" PARTUUID = "0007fd62-01"
/ dev / sdc2: LABEL = "PRTZm_data-common" UUID = "7FB1E3D91206DE1C" TYPE = "ntfs" PARTUUID = "0007fd62-02"
/ dev / sdc3: LABEL = "PRTZm_programming" UUID = "0A69FDE9688969D9" TYPE = "ntfs" PARTUUID = "0007fd62-03"
= - = - = - = - = - =
so far, till now, I tried to reveal the montage of the HD without taking into the account of partitions into which the USB HD is divided ..
But since the blkid command does not reveal its own UUID I am now thinking that this could be the problem.
IN CONCLUSION, since the USB is divided into partitions, ... will the UDEV event reveal the presence of the entire HD (as the sole unit), or will it instead reveal the presence of the three individual different partitions?
Still I would ask .... : this is a good syntax ? ENV{ID_FS_UUID}=="1A5CEE7149E4BA81"
and still also, :-) ....
what I have to use the UUID number, or instead the PARTUUID number ?
thank you very much
Angelo
On Mon, Jul 1, 2019 at 2:00 PM Seth Kenlon <skenlon@xxxxxxxxxx> wrote:
Angelo,
I agree with Tom's analysis, but my udev script accounts for it by
mounting your drive with a very specific designator.
Here is how I have tested this sort of thing before:
0. Get the UUID of your drive with blkid
1. Write a udev script to detect your drive by UUID when attached, and
to execute a test shell script (such as /usr/local/bin/angelo-test.sh)
when the drive is attached
2. Create the script /usr/local/bin/angelo-test.sh to do something
very simle, like echo `date` >> /tmp/backup.log, and make it
executable
3. Reboot
4. Attach your drive, and then look for the execution of your test
script. If there was a /tmp/backup.log created with the correct date
and time in it.
5. Look in /media to ensure that your drive has been mounted as a
unique and persistent entitiy.
If it worked, then change the script to your real backup script.
Continue to test.
If it failed, review your udev script, use `udevadm monitor` to
discover why your drive isn't triggering your script.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
