Re: Updating scripts
Re: Updating scripts
- Subject: Re: Updating scripts
- From: email@hidden
- Date: Fri, 16 Mar 2001 15:12:28 -0800
>
>>>Maybe I'm trying to be too clever...
>
>>>I would like to create a way where the scrip looks at a central
location (whatever that may be - fileserver, something
over program linking) and works out if there's a new version of the script.
If there is, it should copy the new version into the startup items folder
replacing itself and then restart the machine.
I have done something very similar with a slightly different approach. I
keep the scripts that I use as startups in the Scripts folder in the system
folder and have an alias to those scripts in the Startup Items folder. The
script looks on the network for a new version of itself. If it finds one
it copies it to the scripts folder. It then trashes the alias in the
startup disk folder and creates a new alias to the newversion in its place.
I've also thought about having the original move itself into another folder
or to the trash, but instead I simply increment the version number in the
script's name. That way if a new version doesn't work for some reason I
have the previous version available.
>
>>If it was a handful of users, I'd just go round and replace each one
manually. But over 500 users - I need to automate it!
I'm so lazy that even a handful of users justified the time spent!
ES