Re: working with remote log files

Is there any reason why each machine can't run a cron job every two minutes to create an error summary and then report back to you rather than you calling them?

(eg) If you install OpenSSL and Crypt::SSLeay on the remote machines, then you can send the callbacks via SSL.

That way, you are minimising network transfer and reducing the load on the 'host' machine.

.02

cLive ;-)

Comment on Re: working with remote log files

Replies are listed 'Best First'.
Re: Re: working with remote log files by data64 (Chaplain) on Oct 13, 2001 at 23:13 UTC
Can you imagine deploying and keep this software up to date on 100 servers ? Then you would also need to have something in place that checks whether this script is still executing on each server. Just adding my 2cents.	[reply]
Re: Re: Re: working with remote log files by Fletch (Bishop) on Oct 14, 2001 at 04:48 UTC
That's what `rsync` is for. No more difficult than managing anything else on 100s of machines. As for making sure that its still running, have it submit a null report even if nothing went wrong. Then you just have to look for who didn't submit anything to determine if it's not running.	[reply]