11-14-2005
chmod erased a directory(?)
I was attempting to change permissions on a directory, used a 'chmod -rwrwrw DirectoryName' command, and hit enter. Now, that directory shows that it's empty! How could this be? Any Ideas?
Thanks
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Ok, listen.........I was using FTP Works to remove and add some files to a domain server. I messed with chmod button and made it so that no-one could access or their browsers could execute files and 2 or three certain directories. If anyone knows how to use this command and will give me a heads up... (2 Replies)
Discussion started by: jarrell
2 Replies
2. UNIX for Dummies Questions & Answers
I am working on a new UNIX box that has been delivered to us, and noticed that the /home directory has 555 permissions on it (dr-xr-xr-x). Any attempt to create write permissions fails on this directory (such as chmod 777), responding only with a message;
chmod: WARNING: can't change home
... (3 Replies)
Discussion started by: ncarmstrong
3 Replies
3. UNIX for Dummies Questions & Answers
Hey everyone, I was wondering if there was a quicker way to chmod a lot of files than doing what im currently doing.
At the moment, im doing chmod 777 *filename* - but I have a lot of files, sub-directories, sub-files etc etc. And at the moment I see I have to chmod every single file... (3 Replies)
Discussion started by: mo0ness
3 Replies
4. UNIX for Dummies Questions & Answers
i am unable to write to some .php files in the following directory:
drwxr-xr-x 3 headroom max 448 Jun 6 2004 Docs
i already tried this:
chmod +777 Docs
chmod: changing permissions of `Docs': Operation not permitted
thanks for your help! (2 Replies)
Discussion started by: phonedog365
2 Replies
5. Solaris
This is Solaris 10, by the way.
I am aware of ACLs or something like that in Solaris 10 where you can change who can access directories and such that goes beyond the standard permisisons (chmod and rwxrwxrwx).
Although I thought when these were being used, the permissions listing would show a... (12 Replies)
Discussion started by: lyonsd
12 Replies
6. Programming
sprintf(fname, "core.%d", pid);
(void) unlink(fname);
if (ttrace(TT_PROC_CORE, pid, 0, 0, 0, 0) != 0) {
perror("TT_PROC_CORE pass");
Fail();
}
if (chmod(fname, 0) != 0) {
perror("chmod");
Fail();
}
Hi,
If i execute above code,everytime am getting below... (1 Reply)
Discussion started by: mansa
1 Replies
7. UNIX and Linux Applications
i think it is the same in both... Iam i right? (1 Reply)
Discussion started by: sumaiya
1 Replies
8. Red Hat
I am having trouble figuring out how to do a "chmod o-w" for all files under a certain directory, while excluding directories under that certain directory.
I can do
chmod -R o-w /thisdirectory
but that changes permissions of all directories under the directory as well as files. I just... (2 Replies)
Discussion started by: austinharris43
2 Replies
9. UNIX for Dummies Questions & Answers
Hi I tried to use chmod in unix to change my file's permission.
chmod 701 hello.cgi
And it did change my desired file's permission. Yet, the name of the file is changed to hello.cgi* . And therefore I cannot compile it after that. So, I just wondering why there is an extra '*' in the file's... (2 Replies)
Discussion started by: alvin8906
2 Replies
10. Shell Programming and Scripting
does anyone know how to exclude a directory with chown or chmod?
im trying to do something like this
chown $username:$username $directory/*
chown $username:$username $directory/.*
chown $username:$username $directory
and
find $directory/* -type f -exec... (1 Reply)
Discussion started by: vanessafan99
1 Replies
sticky(5) Standards, Environments, and Macros sticky(5)
NAME
sticky - mark files for special treatment
DESCRIPTION
The sticky bit (file mode bit 01000, see chmod(2)) is used to indicate special treatment of certain files and directories. A directory for
which the sticky bit is set restricts deletion of files it contains. A file in a sticky directory can only be removed or renamed by a user
who has write permission on the directory, and either owns the file, owns the directory, has write permission on the file, or is a privi-
leged user. Setting the sticky bit is useful for directories such as /tmp, which must be publicly writable but should deny users permission
to arbitrarily delete or rename the files of others.
If the sticky bit is set on a regular file and no execute bits are set, the system's page cache will not be used to hold the file's data.
This bit is normally set on swap files of diskless clients so that accesses to these files do not flush more valuable data from the sys-
tem's cache. Moreover, by default such files are treated as swap files, whose inode modification times may not necessarily be correctly
recorded on permanent storage.
Any user may create a sticky directory. See chmod for details about modifying file modes.
SEE ALSO
chmod(1), chmod(2), chown(2), mkdir(2), rename(2), unlink(2)
BUGS
The mkdir(2) function will not create a directory with the sticky bit set.
SunOS 5.10 1 Aug 2002 sticky(5)