Linux

Ask something
Discussion Locked

INITTAB

0 helpful
6 replies

by jerome

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

im editting the INITTAB from a remote computer. is there a log i can view if somehow my new entry in the INITTAB caused an error w/o looking at the monitor of the main computer?

if there is none. is the another way to do this.

6 replies

by eujay

You can try looking at /etc/rc.log If there are errors at boot time then most of them will be recorded here.

Hope this helps

eujay

by jerome

sorry for the lack of info.. assuming that the system is already UP and i tried to edit the INITTAB all i have to do is KILL -HUP 1. how can i know that (after the system re-read the INITTAB)whats the error? assuming again that i know that the errorwas caused by the new item added to the inittab

by jerome

hehe.. im not good in explaining things... my head is already turning...
detailed explanation..
i editted INITTAB, i added a process to be respawn everytime it dies.
doing a KILL -HUP 1 will rerun/reinitialized ,(or what ever u may call it), INITTAB.
i would know if an error occurs if the item i added didnt start, just instinct, i would go to the server room and take a look at the monitor attached to that server.
my question.. is there a way i can view the errors w/o looking at the server's monitor...
???

by cavedweller

Telnet to the server you are modifying and look at the syslog and messages. You didn't mention which unix you are using so it's hard to give the exact locations. Usually the logs are in /usr/adm, /var/adm or /var/log. Messages which are displayedon the console also get put in one of these 2 files. Use "tail syslog" to see just the last few lines or "tail -128 syslog | more" to scroll through the last 128 lines (change the number to suit your needs).

This discussion is closed to new replies.