Re: Folder Actions: Threat or menace
Re: Folder Actions: Threat or menace
- Subject: Re: Folder Actions: Threat or menace
- From: Jon Pugh <email@hidden>
- Date: Wed, 23 Jan 2002 11:34:23 -0800
At 1:27 PM -0500 1/23/02, email@hidden wrote:
>
I want to attach a Folder Action to folder on our network. The script will
>
simply record the names and mod dates of files moving into the folder. The
>
folder has been locked to prevent its being deleted, moved or renamed, which
>
also apparently prevents a Folder Action from being attached. It appears that
>
we can unlock the folder, attach the script and relock the folder. It also
>
appears attachment is now permanently enabled, without unlocking the folder.
The key is the creation of an icon file which modifies the folder and holds the custom icon and the reference to the folder action script. Creating this file requires privileges. Once created, it can be modified, since the folder isn't protected from modification.
>
All of this makes our IT guys nervous (they're nervouse about AS in general).
>
They're wondering why Folder Actions needs move/delete/rename access to the
>
folder just to watch it. And I'm wondering, just out of curiosty, why the
>
first attachment seems to defeat the locking mechanism.
It doesn't defeat the locking mechanism, it's just that creating the file requires that the folder be unlocked. Once that's done, everything is kosher.
However, it sounds to me like a simpler solution would be a standard (i.e. non-Folder Action) applet which watches the folder. That wouldn't require that the folder be open, which folder actions requires, and it wouldn't require any modifications which would perturb your IT dudes. You could run the applet on any machine which can access the server, without the limitations of folder actions.
Jon