04-06-2005
Use a CD and boot into single user mode and see what the message logs say.
10 More Discussions You Might Find Interesting
1. SCO
Hi,
Wonder is someone can help.
I've got a server SCO_SV 3.2v5.0.7 PentIII that is located at a different site and is running slow and has been for a week. I've been speaking to a third party who say nothing is wrong with it but its still running slow.
The 3rd party advise it could be a... (2 Replies)
Discussion started by: tez
2 Replies
2. HP-UX
Any ideas on why SAM would take so long to load and initialize? (4 Replies)
Discussion started by: csaunders
4 Replies
3. UNIX for Dummies Questions & Answers
All, This is my interview questions. Let me explain the question. Some one is asking me that, the unix server is running very slow. As a unix unix admin, what are the steps we should follow?? What/which process we should check?? What is the way to find the root cause ? Please let me know.... (8 Replies)
Discussion started by: govindts
8 Replies
4. Red Hat
Hi All,
I'm new here.
i was wondering if anyone could shed a light on the problem i am having.
I use a system for distributing broadband amongst users of for example a hotel, the system was designed by someone in the US and it is based on redhat 2.4 (i know its old) and the system uses... (3 Replies)
Discussion started by: clive306
3 Replies
5. Solaris
I am facing a performance problem on a Solaris 10 Sparc V890 server, it is an old one I know. The first time we realized there is a problem with the server, is the time when ftp transfers are made. There were 4 other identical servers doing much better. Network drivers are checked and there... (3 Replies)
Discussion started by: royalliege
3 Replies
6. Shell Programming and Scripting
Hi,
I am using /usr/ucb/mail for mailing thru script. But mail reaches after 30-40 mins. What can be the reason and also how to check status and related info (1 Reply)
Discussion started by: Deei
1 Replies
7. AIX
Hello,
How can I know if ORACLE Database is running slow due to Memory or due to processing power ?
I have only Oracle Database running on a P4 with 4GB RAM.
Could anyone suggest any tools which can help me determine exactly if it is memory issue or processor issue. (43 Replies)
Discussion started by: filosophizer
43 Replies
8. UNIX for Dummies Questions & Answers
Hello,
My PC seems running slow: OS32 system, Pentium(R)4---2.40Ghz, 1GB RAM, 80GB HDI am running Ubuntu 11.10 (Oneiric Ocelot) alone in this box, which seems very slow to me. Is this normal?
Compared with my other PC (Running XP) with 1.99GHz AMD Athlon 3200+, 2GB RAM,500GB HD, XP and Mint... (11 Replies)
Discussion started by: yifangt
11 Replies
9. Shell Programming and Scripting
Slow runnin script. The problem seems to be the sed calls.
In summary the script reads list of users in file1. For each
username search two files (file 1 & file2) for the username
and get the value in the next line after "=". Compare these
values with each other.
If the same then output... (9 Replies)
Discussion started by: u20sr
9 Replies
10. AIX
Hello,
All the commands on AIX are running very slow.
Below is few stats but I didn't find any issue in cpu or memory reosurces
vmstat
System configuration: lcpu=4 mem=6144MB ent=1.00
kthr memory page faults cpu
----- -----------... (2 Replies)
Discussion started by: Vishal_dba
2 Replies
LEARN ABOUT NETBSD
rbootd
RBOOTD(8) BSD System Manager's Manual RBOOTD(8)
NAME
rbootd -- HP remote boot server
SYNOPSIS
rbootd [-ad] [-i interface] [config_file]
DESCRIPTION
The rbootd utility services boot requests from Hewlett-Packard workstations over a local area network. All boot files must reside in the
boot file directory; further, if a client supplies path information in its boot request, it will be silently stripped away before processing.
By default, rbootd only responds to requests from machines listed in its configuration file. If the client doesn't supply a file name (HP700
series machines don't), the first one listed for this machine will be supplied.
The options are as follows:
-a Respond to boot requests from any machine. The configuration file is ignored if this option is specified.
-d Run rbootd in debug mode. Packets sent and received are displayed to the terminal.
-i interface
Service boot requests on specified interface. If unspecified, rbootd searches the system interface list for the lowest numbered,
configured ``up'' interface (excluding loopback). Ties are broken by choosing the earliest match.
Specifying config_file on the command line causes rbootd to use a different configuration file from the default.
The configuration file is a text file where each line describes a particular machine. A line must start with a machine's Ethernet address
followed by an optional list of boot file names. An Ethernet address is specified in hexadecimal with each of its six octets separated by a
colon. The boot file names come from the boot file directory. The ethernet address and boot file(s) must be separated by white-space and/or
comma characters. A pound sign causes the remainder of a line to be ignored.
Here is a sample configuration file:
#
# ethernet addr boot file(s) comments
#
08:00:09:0:66:ad SYSHPBSD # snake (4.3BSD)
08:00:09:0:59:5b # vandy (anything)
8::9:1:C6:75 SYSHPBSD,SYSHPUX # jaguar (either)
rbootd logs status and error messages via syslog(3). A startup message is always logged, and in the case of fatal errors (or deadly signals)
a message is logged announcing the server's termination. In general, a non-fatal error is handled by ignoring the event that caused it (e.g.
an invalid Ethernet address in the config file causes that line to be invalidated).
The following signals have the specified effect when sent to the server process using the kill(1) command:
SIGHUP Drop all active connections and reconfigure.
SIGUSR1 Turn on debugging, do nothing if already on.
SIGUSR2 Turn off debugging, do nothing if already off.
FILES
/dev/bpf packet-filter device
/etc/rbootd.conf configuration file
/tmp/rbootd.dbg debug output
/usr/mdec/rbootd directory containing boot files
/var/run/rbootd.pid process id
SEE ALSO
kill(1), socket(2), signal(3), syslog(3)
BUGS
If multiple servers are started on the same interface, each will receive and respond to the same boot packets.
BSD
December 11, 1993 BSD