| jeelliso |
06-05-2006 08:28 AM |
You shouldn't have to set a umask.
Unfortunantly I could not recreate your problem. I tried exactly what you did, but I got different results.
Code:
[root@mailman ~]# ls -l
total 164
-rw-r--r-- 1 root root 1510 May 24 05:36 anaconda-ks.cfg
-rw------- 1 root root 1 Jun 1 12:22 dead.letter
drwxr-xr-x 2 root root 4096 May 24 10:42 Desktop
-rw-r--r-- 1 root root 17007 May 26 12:28 grep
-rw-r--r-- 1 root root 311 Jun 2 08:57 index.html
-rw-r--r-- 1 root root 46879 May 24 05:36 install.log
-rw-r--r-- 1 root root 5050 May 24 05:36 install.log.syslog
-rw------- 1 root root 29169 Jun 1 14:36 mbox
drwxr-xr-x 2 root root 4096 Jun 5 09:19 temp
[root@mailman ~]# chmod +777 temp
[root@mailman ~]# ls -l
total 164
-rw-r--r-- 1 root root 1510 May 24 05:36 anaconda-ks.cfg
-rw------- 1 root root 1 Jun 1 12:22 dead.letter
drwxr-xr-x 2 root root 4096 May 24 10:42 Desktop
-rw-r--r-- 1 root root 17007 May 26 12:28 grep
-rw-r--r-- 1 root root 311 Jun 2 08:57 index.html
-rw-r--r-- 1 root root 46879 May 24 05:36 install.log
-rw-r--r-- 1 root root 5050 May 24 05:36 install.log.syslog
-rw------- 1 root root 29169 Jun 1 14:36 mbox
drwxrwxrwx 2 root root 4096 Jun 5 09:19 temp
[root@mailman ~]#
I even tried the chmod with a directory in my /mnt directory, but I got the same results. There is not reason (that I can think of), that you should be getting the error you are getting. Its frustrating. Try and see if it will let you add all write access. If you can't do it this way either, I would try running the command in a different shell. You're probably using the bash shell, so try running it in a csh or sh shell.
Good Luck,
~Justin |
