Re: Job Schedulers (preferably Open Source)
From: William Park (opengeometry_at_yahoo.ca)
Date: 12/21/04
- Next message: Bill Vermillion: "Re: The history of the name 'Root' (as in superuser)?"
- Previous message: Kevin Collins: "Re: Job Schedulers (preferably Open Source)"
- In reply to: Dave Hinz: "Re: Job Schedulers (preferably Open Source)"
- Next in thread: Dave Hinz: "Re: Job Schedulers (preferably Open Source)"
- Reply: Dave Hinz: "Re: Job Schedulers (preferably Open Source)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 21 Dec 2004 02:32:03 GMT
Dave Hinz <DaveHinz@spamcop.net> wrote:
> Anyway. 80 *nix boxes. Hundreds of crontabs. Lots of places for stuff
> to hide, and not trivial to manage. Also, let's say we need to move the
> periodic job up or back for whatever reason. Bit of a pain in the ass
> to log in to each & change the crontab.
>
> If I had a centralized system, ...
Is there reason why those 80 servers can't be consolidated into one (or
two) server, and replaced by 80 thin-clients? That would clean up lots
of infrastructure problem.
-- William Park <opengeometry@yahoo.ca> Open Geometry Consulting, Toronto, Canada Linux solution for data processing.
- Next message: Bill Vermillion: "Re: The history of the name 'Root' (as in superuser)?"
- Previous message: Kevin Collins: "Re: Job Schedulers (preferably Open Source)"
- In reply to: Dave Hinz: "Re: Job Schedulers (preferably Open Source)"
- Next in thread: Dave Hinz: "Re: Job Schedulers (preferably Open Source)"
- Reply: Dave Hinz: "Re: Job Schedulers (preferably Open Source)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|