Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
If you can find which init script is issuing the error message by inspecting the boot message sequence you can run that init script in isolation as root (with a start or a stop argument) and, if it reproduces the error message, you can inspect the init script and determine which command is producing the error.
It's helpful if you give more information like which distro you are running and the exact text of the error message. Depending on the distro you may have the boot messages in one of the /var/log files, perhaps bootmsg or something like that.
Micik, when you find whatever script is running that command (check /etc/init.d), find out if it's putting the network card device name at the end of that line.
The command is incomplete, and should read something like this;
/sbin/route add default gw 18.104.22.168 eth0
Oh, and you might be able to catch the error again by typing "dmesg | less" right after you login (just after the server's rebooted).
P.S: If this server's not networked, that might explain things....
Not all Linux distributions use a configuration file such as this, however, this is a great suggestion.
The "sysconfig" directory would be present in a RedHat-based distro (CentOS, WhiteBoxLinux, Fedora, etc).
@repo: True, most "route" binaries work that way, however in *BSD, Solaris, etc that's not always the case.
(I've long since stopped assuming everyone that posts is using Linux, after that one guy that had NetBSD running on a DreamCast was having kernel problems )
Here, I am. Sorry because of the delay, but I'm not really sure about the exact data you need. cat /etc/issue doesn't not provide me much information except that kernel is version 2.0.33. Also during startup procedure I couldn't see if linux distribution is shown somewhere.
I think this distribution is SUSE linux since it has "yast" and "SuSEconfig" files.
Anyway, when computer is shutting down there is similar error, but instead of add, it is written del.
Anyway, networking is OK, so this is not really a problem but annoying to see such error messages during start and shutdown.