Hi Forum,
Please let me take a "low level" question about what I experienced on my CT. It should be my misunderstanding but it would be good if someone could help to clarify.
On my CT udev mounts a USB device then starts a bash script in the background. This script lunches some bash threads and waits for them to complete. The threads has no common job on any file or resource. In the third level of nesting cp -r chrashes without any error message. It leaves the logging sentence in the middle, so it's really chrashes. rsync does the same but for different files.
The scripts are fully functional if I start them from a root console. Even if started in the background.
Is there any constraint that should be taken into account in these cases on CT or on Armbian or regarding udev rules?
Any tools for such bg processes? Other than logfiles.
Any idea welcomed.
Thank you in advance,
T
Please let me take a "low level" question about what I experienced on my CT. It should be my misunderstanding but it would be good if someone could help to clarify.
On my CT udev mounts a USB device then starts a bash script in the background. This script lunches some bash threads and waits for them to complete. The threads has no common job on any file or resource. In the third level of nesting cp -r chrashes without any error message. It leaves the logging sentence in the middle, so it's really chrashes. rsync does the same but for different files.
The scripts are fully functional if I start them from a root console. Even if started in the background.
Is there any constraint that should be taken into account in these cases on CT or on Armbian or regarding udev rules?
Any tools for such bg processes? Other than logfiles.
Any idea welcomed.
Thank you in advance,
T