I'm a little confused how the described setup in the README is meant to work in Filewave.
If the actual installation step takes place in the fw_softwareupdate_activation.sh script, and set as an activation script in the fileset, won't that only ever run a single time when the fileset is first associated?
As far as I know, verification scripts are the only ones that run on a regular basis but fw_softwareupdates_verification.sh only downloads the updates rather than installing them.
So just curios if I'm misunderstanding something here or if a fileset with these scripts is designed to be re-associated on a regular basis so that fw_softwareupdate_activation.sh will run again.
I'm a little confused how the described setup in the README is meant to work in Filewave.
If the actual installation step takes place in the
fw_softwareupdate_activation.shscript, and set as an activation script in the fileset, won't that only ever run a single time when the fileset is first associated?As far as I know, verification scripts are the only ones that run on a regular basis but
fw_softwareupdates_verification.shonly downloads the updates rather than installing them.So just curios if I'm misunderstanding something here or if a fileset with these scripts is designed to be re-associated on a regular basis so that
fw_softwareupdate_activation.shwill run again.