Shell Programming and Scripting

But, ok, it is not probably the best way to write out a script like this, but I don't see any comments that are talking about something that is WRONG, not bad, but WRONG. I am looking for WRONG things! And I didn't find them, and, as I see you didn't neither!

@hackermania
It would really help to know what Operating System you have. The "ls" command looks like a Linux variant but the shebang line says "sh" (not "bash").

Without seeing the error messages we are guessing.

I believe that one bug is that when the "root" account deletes the directory it then re-creates the directory with ownership "root" and all files created in that directory are owned by "root". With a default "umask" no other user can delete that directory or the files in that directory.


As others suggest the logic may also be flawed but we do tend to think about unix servers with hundreds of accounts.

I am using Ubuntu 9.10.
There aren't really a lot of error messages. The thing is that even if there isn't any folder or file which has the name of a user, when root runs the program, behaves like there is a folder or a file with the name of a user, and executes ./cleaner, no ./runit as it should be.

---------- Post updated at 02:17 AM ---------- Previous update was at 01:08 AM ----------

Ok guys, I solved the problem. The problem was that if the $user3 for example was an empty string returns true value in the command if [ -s "$currentpath"/$user3 ]; then mpla mpla mpla
so i had some ifs to check if the $userX variables were an empty string, and if they were, then the program avoids even to search for them in the current directory. And that worked just fine
Many thanks to all of you for your valuable help!

Here are many solutions. You can apply one.