Dave share defs?

[Allen Reese]

More than likely what this script does is for the MacOS and not DAVE....

When i copy files from my MacOS boxes to my netatalk shares they usually
are 777...  ;)

Allen Reese
Senior Software Engineer
Driversoft, Inc.
allen at driversoft.com

On Wed, 24 Feb 1999, Beito wrote:

> On Wed, 24 Feb 1999, Andy Alsup wrote:
> 
> > I have been a little worried about the data fork and resource fork
> > issue with Dave, but I'll assume that if I can copy to the volume and
> > still execute or open a file, everybody is happy. Is this a safe
> > assumption? 
> 
> Here in the Fine Arts department, we've had a script that needs to be run
> everytime we add an app to the network drive that is shared among a lot of
> users.  I'm not sure who wrote it.  I inherited it, and they didn't put it
> in comments anywhere.  I'm sure there's a better solution to this, but
> I haven't had time to play with it with classes going on and other
> disasters occurring...
> 
> ---------cut me---------------
> #!/bin/csh
> # Progname: setdaveperms
> # Author  : ???
> ####################################
> if ($1 == "") then
>         cat << EOF      
> 
> Usage:  setdaveperms path
> 
> EOF
> else
>         # First, recurse through and set all the directory permissions to
>         # 1755.  The one sets the "sticky bit" which is used to safeguard 
>         # against renames and moves.
>         find $1 -type d -exec chmod 1755 {} \;
> 
>         # Next, recurse through and set all the file permissions in the
>         # dirctories to 777.  Now, you see why the sticky bit was set!
>         find $1 -type f -exec chmod 777 {} \;
> endif
> 
> exit
> ---------cut me---------------
> 
> -- 
>            Matt Beito   mabeito at mtu.edu   
>    "It's tragic that a family can be torn apart 
>  by something as simple as wolves..." - Anonymous
> 
> 
>