Post #1427889
2026-03-23 14:18 UTC
Just in case, there are no spaces or weird characters anywhere in the directory path or any of the filenames. The weirdest anything gets is a dash/hyphen. Full pathnames are are along the lines of /home/kagan/Pictures/foo-1234.jpg and suchlike, plus one file that has underscores.
And again, it works fine when I run it from the command line, so I don't understand why it fails from the menu or crontab. I've tried everything I can think of. Has anyone got any ideas? Thank you. Boosts welcome. 4/4
Replies (2)
-
@surefire@infosec.exchange 2026-03-23 14:34
@kagan Without seeing the script itself, two thoughts: Make sure the script starts with a #! line, since that tells the OS what kind of script it is. Since you mentioned being able to touch a file, write to a log file to see exactly where it is hanging: #!/bin/bash echo 0 >> mylogfile (first line of code here) echo 1 >> mylogfile (second line of code here) echo 2 >> mylogfile (third line of code here) ...
-
@rootwyrm@weird.autos 2026-03-23 14:56
@kagan I've seen this behavior many times, so much so that I don't need to see the script to know what it is. Something in there is hanging because it expects or demands stdout/stderr.