Setting a more aggressive trigger for some rules

Hi,
I have a rule that mounts my NAS folders if the NAS is available (using Applescript to ping it and mount it). I have it running on the /Volumes folder and for the most part it works well... except that occasionally the drives aren't mounted even though I'm on my home network.
In some cases, I imagine this could be because of a race condition with the network coming online, maybe the rule is running before the NAS is pingable.
But then I realized that if I sue my laptop outside the house, then on returning, there won't be any change in /Volumes -- the disappearance of the network drives happened while I was out.
So, in order of (my) preference:
1) Hazel could have specific support for /Volumes, understanding that network changes, sleep/wake, etc are all triggers for rules on this folder.
2) Hazel could offer some other brute-force mechanism: run rules on a timer, for example.
3) I could make my current rule have some side-effect when the NAS isn't available (e.g. touch a file somewhere), which I can then use to trigger a re-try later. This sounds hard to do, and at best would be a gross hack. But maybe I'll give it a shot.
Thoughts? Other ideas? I'm very new to Hazel, so if I'm missing something basic, I'll be happy to learn the right way to do this
I have a rule that mounts my NAS folders if the NAS is available (using Applescript to ping it and mount it). I have it running on the /Volumes folder and for the most part it works well... except that occasionally the drives aren't mounted even though I'm on my home network.
In some cases, I imagine this could be because of a race condition with the network coming online, maybe the rule is running before the NAS is pingable.
But then I realized that if I sue my laptop outside the house, then on returning, there won't be any change in /Volumes -- the disappearance of the network drives happened while I was out.
So, in order of (my) preference:
1) Hazel could have specific support for /Volumes, understanding that network changes, sleep/wake, etc are all triggers for rules on this folder.
2) Hazel could offer some other brute-force mechanism: run rules on a timer, for example.
3) I could make my current rule have some side-effect when the NAS isn't available (e.g. touch a file somewhere), which I can then use to trigger a re-try later. This sounds hard to do, and at best would be a gross hack. But maybe I'll give it a shot.
Thoughts? Other ideas? I'm very new to Hazel, so if I'm missing something basic, I'll be happy to learn the right way to do this
