I'm pretty sure this is a SAMBA issue. I have a strange problem when changing permissions on a file (ex. index.html) through Windows on a SAMBA share. For example: All user files are accessed through SAMBA Through W2K, I set the permission on my index.html file so that only the user has read/write and nothing for group and Everyone. Now this should break my web page, but to my surprise it still loads!!! I check the permission of the file on the UNIX server, sure enough the index.html file shows mode 600. Hmmmm, next I check the to see what the perms look like on the Web server. Sure enough it shows mode 600 too?!?!?!?! And yet the page still loads in my browser. So I restart Apache, the page still loads; I restart the nfs daemons on the web server, the page still loads; I make sure and empty my memory cache and disk cache on my browser, the page still loads!!!! Its only after I do a "chmod 600 index.html" (in UNIX) again, that the page finally breaks and I get the 403 error. One other test I did was to 'su' to the apache user. Even though the index.html file was mode 600 it could still read the file. But again after doing a "chmod 600" in UNIX then the apache user could not read the file. Has anyone else seen this behavior? This happens on SAMBA shares for both Linux and Solaris. Apache version: 1.3.19 SAMBA version: 2.2.5 Linux: RH 7.2 Solaris 8 I just want the chance to prove 'Money can't buy Happiness'" - a bumper sticker C. J. Keist Email: cjay@engr.colostate.edu UNIX/Network Manager Phone: 970-491-0630 Engineering Network Services Fax: 970-491-5569 College of Engineering, CSU Ft. Collins, CO 80523-1301 -------------- next part -------------- HTML attachment scrubbed and removed
Sorry if this comes in twice, but Eudora was still showing this in my send queue. I'm pretty sure this is a SAMBA issue. I have a strange problem when changing permissions on a file (ex. index.html) through Windows on a SAMBA share. For example: All user files are accessed through SAMBA Through W2K, I set the permission on my index.html file so that only the user has read/write and nothing for group and Everyone. Now this should break my web page, but to my surprise it still loads!!! I check the permission of the file on the UNIX server, sure enough the index.html file shows mode 600. Hmmmm, next I check the to see what the perms look like on the Web server. Sure enough it shows mode 600 too?!?!?!?! And yet the page still loads in my browser. So I restart Apache, the page still loads; I restart the nfs daemons on the web server, the page still loads; I make sure and empty my memory cache and disk cache on my browser, the page still loads!!!! Its only after I do a "chmod 600 index.html" (in UNIX) again, that the page finally breaks and I get the 403 error. One other test I did was to 'su' to the apache user. Even though the index.html file was mode 600 it could still read the file. But again after doing a "chmod 600" in UNIX then the apache user could not read the file. Has anyone else seen this behavior? This happens on SAMBA shares for both Linux and Solaris. Apache version: 1.3.19 SAMBA version: 2.2.5 Linux: RH 7.2 Solaris 8 I just want the chance to prove 'Money can't buy Happiness'" - a bumper sticker C. J. Keist Email: cjay@engr.colostate.edu UNIX/Network Manager Phone: 970-491-0630 Engineering Network Services Fax: 970-491-5569 College of Engineering, CSU Ft. Collins, CO 80523-1301 -------------- next part -------------- HTML attachment scrubbed and removed
Is anybody out there???? I'm pretty sure this is a SAMBA issue. I have a strange problem when changing permissions on a file (ex. index.html) through Windows on a SAMBA share. For example: All user files are accessed through SAMBA Through W2K, I set the permission on my index.html file so that only the user has read/write and nothing for group and Everyone. Now this should break my web page, but to my surprise it still loads!!! I check the permission of the file on the UNIX server, sure enough the index.html file shows mode 600. Hmmmm, next I check the to see what the perms look like on the Web server. Sure enough it shows mode 600 too?!?!?!?! And yet the page still loads in my browser. So I restart Apache, the page still loads; I restart the nfs daemons on the web server, the page still loads; I make sure and empty my memory cache and disk cache on my browser, the page still loads!!!! Its only after I do a "chmod 600 index.html" (in UNIX) again, that the page finally breaks and I get the 403 error. One other test I did was to 'su' to the apache user. Even though the index.html file was mode 600 it could still read the file. But again after doing a "chmod 600" in UNIX then the apache user could not read the file. Has anyone else seen this behavior? This happens on SAMBA shares for both Linux and Solaris. Apache version: 1.3.19 SAMBA version: 2.2.5 Linux: RH 7.2 Solaris 8 I just want the chance to prove 'Money can't buy Happiness'" - a bumper sticker C. J. Keist Email: cjay@engr.colostate.edu UNIX/Network Manager Phone: 970-491-0630 Engineering Network Services Fax: 970-491-5569 College of Engineering, CSU Ft. Collins, CO 80523-1301 -------------- next part -------------- HTML attachment scrubbed and removed