On Sat, 17 Mar 2001, Philips wrote:
> Ray Olszewski wrote:
> >
> > At 01:21 PM 3/16/01 +0200, Philips wrote:
> > >Hello All!
> > >
> > > I've set up new PC Linux server box and I'm looking for way to have a
>shell on
> > >it.
> > > I thought telnet/ssh will be enough - but network should be up and
> > >reconfiguring network is almost impossible.
> >
> > NO, just very tricky. I've remotely admin'd hosts for months without seeing
> > them (once I had the initial setups right).
>
> last time I tried to upgrade inetd service using telnet... You can understand
> what happened - due to upgrade inetd was shut down, while shutting down inetd
> killed my own shell... As soon as my shell was killed - it killed current job
> - upgrade process was interrupted :-(((
I like Ray also operate many severs via remote logins, some of which are
thousands of miles away from me.
When doing work like you talk of i write a small bash script to do the job and
restart the daemon(s) allowing me to login after the work is done.
I would use something like the following, it is simple and to the point. Of
course you can make the srcipt more complecated its just what one wants and
needs.
This scripts does;
Creates or cleans out a file called /tmp/tmpdata which is used as logfile.
Places the date in the log.
Untar's a file called xconvers-0.6.tar.gz located in my home directory.
runs the configure script.
make the program.
installes it.
See the tarfile as you installing a new inet daemon.
After its been made and installed the "if" statement checks to see if inetd is
running, if it is it is told to reread its config file (kill -HUP) if it is not
found inetd will be started.
#!/bin/sh
DATA="/tmp/tmpdata"
if [ -f $DATA ]; then
> $DATA
/bin/date > $DATA
else
touch > $DATA
/bin/date > $DATA
fi
tar xzf /home/pa3gcu/xconvers-0.6.tar.gz >>$DATA
cd xconvers-0.6
./configure >>$DATA
make >>$DATA
make install >>$DATA
PS=`ps ax | grep -v grep | grep inetd | awk '{print $1}'`
if [ "$PS" -gt "0" ]; then
kill -HUP $PS
else
inetd &
fi
>
> >
> > > Terminal on serial port is nice - but any cable/terminal troubles will
>force
> > >me to shutdown server. too bad... :-(
> >
> > I don't understand what this means. If you set up your inittab entry right,
> > the server should survive terminal or cable problems quite well.
> >
>
> but most motherboards will not.
> I have at least 2 motherboard with broken (integrated) serial controlers,
> because of some peoples who like to pull the plugs from turned on PC... :-(
I have never seen one which gets broken because someone pulls the plug or
places one into a socket. Its a question of doing it properly.
>
> >
> > You will need to be a bit more specific about what you actually need/want to
> > get more detailed advice.
> >
>
> I have a network server. Server has no monitor/keyboard.
> I need a way to upgrade some network packages.
> Doing this using telnet/ssh is impossible because upgrade process may require
> network restart. Using serial cable will tie one PC (I do not have this one) to
> the server.
>
> PS I'm using Debian 2.2 for server. SuSE 6.2 is running on my desktop.
--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
