On Fri, 2005-01-21 at 12:34 -0500, Phill wrote: > >>> > > > >Run a cron job on the workstations to run a script stored on the server > >if it exists would be simple but effective. > > > > > > > Not really, innit? I mean, aside from security issues, I can't tell them > to do something on demand - I have to wait till the 30 or so machines > parse the file every so often (which you probably don't want them doing > every 30 seconds).
30 PC's checking a file on the network every minute doesn't add up too much traffic. > What if I only want to shutdown/update 5 machines? learn how to script and use the hostname and touch commands. > Maybe I want to kill a specific application on this users machine. use ssh, you were on about multiple machines before. > It's an extra level of abstraction and unnecessary complication, I'd say. don't be so negative it was only an idea, pssh looks good (never seen it before dirk mentioned it). > To give you an example of what I was aiming at, take Apple Remote > Desktop. It essentially works like a mass vnc observer; we can give the > computers simple commands, take them over and install stuff on them or > push files over the network. Sometimes we catch kids (this is a school > place I'm talking about afterall) trying to run games or monkeying > around - you log into ARD and just take over his computer. > Just sayin'. Your thinking Windows world with maintaining many PC's. Look at AFS, one filesystem many machines, makes maintaining multiple machines easy. ssh server on the workstation is always handy for remote access / maintenance. Use VNC (rdesktop) for to observer/remote control there X session. -- [email protected] mailing list
