On Thu, Jul 01 at 08:58AM +0800, John Summerfield wrote: > Mark Ferlatte wrote: > > >Will Trillich said on Wed, Jun 30, 2004 at 04:34:06PM -0500: > >>questions: > >> 1) what's the best way (e.g. debian way) to monitor active > >> daemons and restart them when necessary? maybe some > >> utility already exists for this? or /proc/something? > >> or `ps ax`? > > > >monit can do this. > > As can webmin.
webmin would be promising if we already had all that overhead running. (plus i've seen it have problems -- for ecsample, "apache-lib.pl" is missing in a few installations i've seen, and it borks the html interface when a piece like that is absent.) plus, the webmin code itself looks like it's right out of the seventies. hoo boy! -- I use Debian/GNU Linux version 3.0; Linux boss 2.4.18-bf2.4 #1 Son Apr 14 09:53:28 CEST 2002 i586 unknown DEBIAN NEWBIE TIP #69 from Will Trillich <[EMAIL PROTECTED]> : Preparing to UPGRADE POSTGRESQL? If you have a second machine on your network that you can tinker with, do your upgrade there, first: once tested, you can just have your current applications link to the remote database through the network: psql -h 192.168.2.17 myDB or in perl, $dbh = DBI->connect('dbi:Pg:dbname=myDB;host=192.168.2.17'); (You may need to tweak your 'host-based access' settings in /etc/postgresql/pg_hba.conf, first.) Once you're satisfied that all is well, upgrade your main server. No down time! See "man psql" and "man DBD::Pg" for details. Also see http://newbieDoc.sourceForge.net/ ... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]