Hi Gaurav,
There is no directory called check in the etc directory and
it seems to be that there is no shutdown.allow in my system(i used "locate
shutdown.allow" command)
BTW, i am issuing a reboot command, only after  logining(through telnet) as a
normal user and then using su commnad to get the root privilages.
Is is it appropriate to issue a reboot command( as a root only) from a
remote(telnet) terminal

I have not got a chance to check the exit code of e2fsck. next time if is issue
a reboot, i will let u know.


Srinivas.A.V.









"Gaurav Yadav" <[EMAIL PROTECTED]> on 07/03/2000 02:29:33 PM

Please respond to [EMAIL PROTECTED]

To:   [EMAIL PROTECTED]
cc:    (bcc: A V Srinivas/Systems/NSEIL)

Subject:  Re: [LIH] Problem with the reboot command from a telnet terminal




hope this gives you a way out.
[EMAIL PROTECTED] wrote:

> We have a server installed with SuSE 6.3 Linux.. When i try to give a
> reboot/shutdown -r now command
> from a remote terminal( telnet)  the server is not properly restarting. every

this may hapen because every program which will be running(remotely) starts with
root priveledges and then the
previledges are changed to the user who is telnetting i.e. mr. X.
check /etc/check shutdown.allow file


>
> time i have to go to server room and login as
> root( infact it is saying that file system is corrupted and requires a root
> password). and use the command e2fsck -y dev/hda3.

this may happen because you may have e2fs super block corrupted which e2fsck
detects
when you run it ( based on flags)
and corrects it as it has backup of blocks making super block.
check the exit code of e2fsck and try to figure the error using the man page of
e2fsck.
-y option disables human interfernces to allow the linux to work on its own
ways.

>
> After this, i have to give a reboot command again to put that server into
normal
> state.

this rebooting checks for the flag and does a forcibly fsck.
and everything runs fine again.

>
> Any one can tell me what is going on. how can i solve this probelm.

most probably your super block is corrupted, try to analyse the exit code of
e2fsck.



>
>
> TIA
>
> Bye,
> Srinivas.A.V.
>

-gaurav.

>
> -----------------------------------------------------------------------
> The LIH mailing list archives are available at:
> http://lists.linux-india.org/cgi-bin/wilma/linux-india-help

--
  _
|^|^|                         -^-                     Love to Linux
 \-/ G  A  U  R  A  V          |
mailto:[EMAIL PROTECTED] / mailto:[EMAIL PROTECTED]
  | Sea/She is nature's art/\/ Everybody likes to get the feel of it
|-=-----------------------/-----------------------------------------|
|_|f  I  can  I m a g i n/e  it  I  can  A c h i e v e  it_._.-.-._.|



-----------------------------------------------------------------------
For more information on the LIH mailing list see:
http://lists.linux-india.org/lists/LIH







-----------------------------------------------------------------------
For more information on the LIH mailing list see:
http://lists.linux-india.org/lists/LIH

Reply via email to