[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Re:[cobalt-users] Suspending servers
- Subject: Re: Re:[cobalt-users] Suspending servers
- From: Rik Thomas <rikt@xxxxxxxxxxxx>
- Date: Thu Dec 14 07:56:01 2000
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Well your best bet is to limit their types of access at the switch level,
with cisco switches you could allow inbound port 25, and disallow
everything else, or a mix of what you want to allow and disallow. We
generally do it at the switch level.
On Thu, 14 Dec 2000, The Thieving Gypsy wrote:
>
> > >I need to suspend the server of one of my clients. The problem is, I
> want
> > >to leave them with limited access - simply unplugging the server would
> cause
> > >all sorts of bother over lost emails, etc. I plan on stopping the httpd
> and
> > >admserv daemons, and then suspending their telnet accounts, but am not
> quite
> > >sure whta th implications are... My client has access to the admin
> password
> > >(and therefore the root) account, but I have set up another root account
> for
> > >my use. My question is, which of the clients accounts should I suspend -
> > >the admin account, or the root account? What would the implications be
> of
> > >suspending the admin account if, for example the server crashed? Also,
> > >could suspending the root account have nasty repercussions?
--
Rik Thomas CTO rikt@xxxxxxxxxxxx
Delaware.Net, Inc. http://www.delaware.net
P:302.736.5515 F:302.736.5945 ICQ:879956
--
$20 Domains!!! http://register.delaware.net