Hi!
I remembered that this happened to me many many times. So this is a typical
777 problem as described above. But if you have a root access and those directories were created by different users then may be there could be a connflict.
Try out anathor command which is a bit different than chmod.
chown user.group directory
OR
chown user.group *
This changes the ownership of a directory or a file to the specified name.
For e.g. if the owner of the scripts and directories is nobody and if the directory it is trying to create does not allow because it belongs to the a normal user , then this may be, may be, may be a reason.
Though this is just an idea, the perl freaks and unix master may think
such a condition could never happen. So I could be wrong.
By giving the command
dir
OR
ls
it will show you the ownerships and related conflicts.
I remembered that this happened to me many many times. So this is a typical
777 problem as described above. But if you have a root access and those directories were created by different users then may be there could be a connflict.
Try out anathor command which is a bit different than chmod.
chown user.group directory
OR
chown user.group *
This changes the ownership of a directory or a file to the specified name.
For e.g. if the owner of the scripts and directories is nobody and if the directory it is trying to create does not allow because it belongs to the a normal user , then this may be, may be, may be a reason.
Though this is just an idea, the perl freaks and unix master may think
such a condition could never happen. So I could be wrong.
By giving the command
dir
OR
ls
it will show you the ownerships and related conflicts.