drysdalks idea was a good one, but i think now is he time to resort to good old debugging techniques:
Quote:
Originally Posted by
anaigini45
However, the scripts remained not executable.
What exactly do you mean by that? Obviously the execute-privilege of these were not changed, no? So, how did the fail? Error messages? Log entries? Exit codes? Smoking guns?
Quote:
Originally Posted by
anaigini45
Is it possible that when I deleted /var/tmp, some symlinks were removed?
And therefore any of the problem scripts had some symlink from /var/tmp?
Yes, this
might be possible, but yet again the opposite is equally possible. Instead of making wild guesses, you might want to analyse the problem - see above: try something, gather evidence, analyse it, then start over.
Quote:
Originally Posted by
anaigini45
I cannot think of any other reason why there could be scripts which became not executable even after I had restored the directory.
This is the good thing about good debugging practice: you don't have to be overly creative in this regard. If a script you try to start fails with
Error: failed to make the flurbishes grommicking it is quite obvious what happened.
If the script(s) you start fail to give any conclusive error message (in this case: shame on the programmers!) then look inside the scripts and search for the string "/var/tmp" to try to locate the places where it tries to access the directory in question.
I hope this helps.
bakunin