A Samuel Adams at that!! > From: Schoun Regan <schounregan at mac.com> > Reply-To: macgroup at erdos.math.louisville.edu > Date: Wed, 10 Sep 2003 22:50:04 -0400 > To: <macgroup at erdos.math.louisville.edu> > Subject: Re: MacGroup: cron job and file permissions > > Came late to the game. Busy-sorry bout that. > Jerry, just bust out a 'lil ole script there; chmod this and 777 that and > we're all set! > Matt, > How are the Apple File Sharing permissions set on the server? > I bet they are set to "Use standard UNIX behavior" > Change it to Inherit permissions from parent. > Reboot. > If it works you owe me a beer. > If not, I'll take another crack at it. > > Schoun > > > > > >> From: estate <estate200 at yahoo.com> >> Reply-To: macgroup at erdos.math.louisville.edu >> Date: Wed, 10 Sep 2003 16:26:26 -0700 (PDT) >> To: macgroup at erdos.math.louisville.edu >> Subject: Re: MacGroup: cron job and file permissions >> >> Thnanks Jerry, >> >> I think your right. It would be better to determine why the user is doing >> this >> thing. I'm always >> nervous about running a script that affects so much all at once. We have >> nightly backups but >> still...) >> >> If they knew what a terminal was I might not even have a problem! ;) >> Plus I always have "0 0 * * * shutdown -h 2" on a client machine as a >> payback! >> >> anyway thanks for the feedback. >> >> matt >> >> --- Jerry Yeager <jerry at browseryshop.com> wrote: >>> Of course, if Bob and Sue are determined to have some fun at the >>> sys-admin's expense, AND they know that a quick trip to Terminal (chmod >>> 755 filename) before uploading it to the server will allow them time to >>> bug the sys-admin before the CRON script kicks in -- unless you set it >>> to run every minute which is not advisable. >>> >>> Just looking at the possibilities... >>> >>> Jerry >>> >>> On Wednesday, September 10, 2003, at 05:20 PM, estate wrote: >>> >>>> Hello! >>>> >>>> I've been lurking here for a few days but now I have a question! >>>> >>>> My department has a Xserve and about 7 Mac client machines. All >>>> clients fileshare with the Xserve >>>> and do not netboot. Some folks are transferring files over that have >>>> read-only group priviliges >>>> and others in the group open the file, edit but cannot save it. >>>> >>>> Example: >>>> clients (bob, sue) transfer files to Xserve (where they log in as a >>>> user who are in the same >>>> group) (bob in dept A, sue in Dept A). Bob transfers file foo.txt to >>>> the Xserve. Sue opens foo.txt >>>> but cannot save it because Bob copied it in a way that the Group write >>>> priviliges are missing. >>>> >>>> This is causing me headaches. I want to run a cron job every night >>>> that sets all files under a >>>> particular folder to 775 (rwx rwx r-x). Now, is this a bad idea for >>>> reason that I don't know >>>> about? This will affect tens of thousands of files every night. Or can >>>> someone tell me / point me >>>> to site as to why my clients are copying files to the Server >>>> incorrectly. >>>> >>>> thanks for any advice. >>>> >>>> matt >>>> >>>> >>>> >>>> >>>> | The next meeting of the Louisville Computer Society will >>>> | be September 23. The LCS Web page is <http://www.kymac.org>. >>>> | This list's page is <http://erdos.math.louisville.edu/macgroup>. >>>> >>> >>> >>> >>> | The next meeting of the Louisville Computer Society will >>> | be September 23. The LCS Web page is <http://www.kymac.org>. >>> | This list's page is <http://erdos.math.louisville.edu/macgroup>. >> >> >> | The next meeting of the Louisville Computer Society will >> | be September 23. The LCS Web page is <http://www.kymac.org>. >> | This list's page is <http://erdos.math.louisville.edu/macgroup>. > > > > | The next meeting of the Louisville Computer Society will > | be September 23. The LCS Web page is <http://www.kymac.org>. > | This list's page is <http://erdos.math.louisville.edu/macgroup>.
| The next meeting of the Louisville Computer Society will | be September 23. The LCS Web page is <http://www.kymac.org>. | This list's page is <http://erdos.math.louisville.edu/macgroup>.
