[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Continuing curiosity re Cobalt GUI & Webmin
- Subject: Re: [cobalt-users] Continuing curiosity re Cobalt GUI & Webmin
- From: shimi <shimi@xxxxxxxxxxxxxxxx>
- Date: Sat May 26 03:42:34 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
On Sat, 26 May 2001, Colin J. Raven wrote:
> Greetings Gang!
> I've been fermenting this train of thought for a while. It concerns
> webmin and our GUI....NOT one *versus* the other, but how they play
> together...or if they play together at all.
> Here's the general direction as concisely as I can put it:
> We know that our GUI writes to files, we know that webmin writes to
> files...which is the entire raison d'etre for using either one of
> course.
> HOWEVER....
> If both exist, files written to by webmin (if it was invoked) would be
> overwritten by our GUI at next reboot...yes? no?
> SO.....
> 1. CAN our GUI be disabled completely if one happens to prefer webmin?
> (no, I'm not evangelizing either one, just pondering)
> 2. HOW would one go about killing our GUI if webmin was (or became) the
> interface of choice??
> OR....
> Is this just a waste of bandwidth publicly wondering about such
> sacrilegious matters?
>
> Regards,
> -Colin
To stop all Cobalt's GUI operations, one needs to:
a) stop it from loading on boot. chmod 644 /etc/rc.d/init.d/admserv will
do the trick, in my opinion.
b) stop all cobalt-related cronjobs. (only active monitor, unless someone
else thinks otherwise, and I stand to be corrected)
In file /etc/crontab, comment (add a leading #) the last line, :
0,15,30,45 * * * * root /usr/local/sbin/swatch >>/var/cobalt/adm.log 2>&1
Comments? I'm listening! :-)
HTH,
- shimi.