<html>
<head>
</head>
<body>
I created a new Temp User with the the umask 022, and it did create the right
file permissions at least for a short while, but then even they got rubbed
out. What about the "fstab" issue? Could that be the problem?<br>
<br>
<br>
<i>/dev/hda7 / xfs defaults 1 1<br>
none /dev/pts devpts mode=0620 0 0<br>
none /dev/shm tmpfs defaults 0 0<br>
<b>/dev/hda8 /home xfs defaults 1 2</b><br>
/dev/hda6 /storage ext2 defaults 1 2<br>
/mnt/cdrom /mnt/cdrom supermount dev=/dev/scd0,fs=iso9660,ro,--,iocharset=iso8859-1
0 0<br>
/mnt/floppy /mnt/floppy supermount dev=/dev/fd0,fs=vfat,--,iocharset=iso8859-1,umask=0,sync,codepage=850
0 0<br>
/dev/hda1 /mnt/windows vfat iocharset=iso8859-1,umask=0,codepage=850 0 0<br>
none /proc proc defaults 0 0<br>
/dev/hda5 swap swap defaults 0 0</i><br>
<br>
<br>
<br>
MonMotha wrote:<br>
<blockquote type="cite" cite="mid:3CEC5DBB.3040707@indy.rr.com">Both related
and unrelated, UMASK only applies at creation time, not later on. So if
I were to create a file and my UMASK was 022, I would get 755 permissions,
or rwxr-xr-x. If my UMASK is 002, I get rwxrwxr-x, which may be appropriate
when each user has their own group (so you may have it backwards?). <br>
<br>
In any circumstance, umask only applies at file creation, not later. So
this means that there must be some sort of daemon or cron script adding
permissions. It's possible that this was accidentally enabled by the user,
but it is disturbing nonetheless. <br>
<br>
-</blockquote>
<br>
</body>
</html>