12-19-2017
Possibly the system has run out of network buffer resources. Has the load/number of users been steadily increasing?
Network configurations determine the number of buffers available for network packets (of various different sizes) arriving and departing, and also the maximum number of connections.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi I am using unix for last few days. Here is my problem
during boot the machine stop giving video signal and I don't know what's happening.
When I ping (during boot) it from another machine it comes alive then goes out.
The power on the CPU is on all the time.
please help. (9 Replies)
Discussion started by: santosh1981
9 Replies
2. UNIX for Dummies Questions & Answers
Is it common in the Unix/Linux environment to install compute intensive applications on a Server system and have the client machines download the executables into memory at runtime to run locally? This model seems taxing to the network, and as I understand, has been largely abandoned in the... (1 Reply)
Discussion started by: jonwillog
1 Replies
3. UNIX for Advanced & Expert Users
Hi,
When most of the server applications get installed, they create their own user. I believe this is to not use the "root" account. For example, Apache when installed creates a user called "apache". And the directories which it uses are all owned by this user. This seems to be the... (2 Replies)
Discussion started by: srikanths
2 Replies
4. Shell Programming and Scripting
Hi all
I am running a major script of my application in development for implementing code changes for process improvement in time. The script runs in production once in a month . It takes 8 hours 30 mins in Production server . what surprice me is , when I run the same script in development server... (9 Replies)
Discussion started by: sakthifire
9 Replies
5. Programming
hello all,
I have developed a server application in C for ulinux kernel 2.6.It works very fine; creating a socket, binding it to a port, listening for incoming sockets and accepting them ,all finish without any error.
But there is a problem regarding application crash.After an intentionally... (1 Reply)
Discussion started by: Sedighzadeh
1 Replies
6. Programming
Problem
- Linux Client/Server Socket Application: Preventing Client from quitting on server crash
Hi,
I am writing a Linux socket Server and Client using TCP protocol on Ubuntu 9.04 x64.
I am having problem trying to implement a scenario where the client should keep running even when the... (2 Replies)
Discussion started by: varun.nagpaal
2 Replies
7. Solaris
Hi there,
We have a Solaris 10 machine which has been up and running for more than 400 days. A strange behaviour happened. The system date defaulted to epoch timestamp. Oracle stopped and application failed causing management to parade. We managed to reset the date. All other servers and... (8 Replies)
Discussion started by: sundar63
8 Replies
8. Red Hat
I encounter the following crash on RHEL 7.0 when I run a multithreaded video rendering application using GLFW and OpenGL. OpenGL version is 2.1 and MESA version is 9.3.0
Following is the back trace of the multi-threaded program I am working on:... (0 Replies)
Discussion started by: anuachin
0 Replies
LEARN ABOUT ULTRIX
ruptime
ruptime(1c) ruptime(1c)
Name
ruptime - show host status of local machines
Syntax
ruptime [ options ] [ machinename ]
Description
The command gives a status line like for each machine on the local network. If a machinename is given, the status of only the named
machine is given. These status lines are formed from packets broadcast by each host on the network once a minute.
Machines for which no status report has been received for 5 minutes are shown as being down.
Options
-a Users idle an hour or more are not counted unless this option is specified.
-d Display only those hosts that are considered down.
-l Sort the status list by load average. If more than one sort option is given, uses the last one.
-r Show only hosts that are up and running.
-t Sort the status list by uptime. If more than one sort option is given, uses the last one.
-u Sort the status list by number of users. If more than one sort option is given, uses the last one.
-nn Show only those hosts with nn or more users.
Restrictions
Because the daemon sends its information in broadcast packets it generates a large amount of network traffic. On large networks the extra
traffic may be objectionable. Therefore, the daemon is disabled by default. To make use of the daemon for both the local and remote
hosts, remove the comment symbols (#) from in front of the lines specifying in the file.
If the daemon is not running on a remote machine, the machine may incorrectly appear to be down when you use the command to determine its
status. See the reference page for more information.
If a system has more than 40 users logged in at once, the number of users displayed by the command is incorrect. Users who login to a
machine after that point fail to increment the user count that appears in the output of the command. This is due to the maximum size limit
of an Ethernet packet, which is 1500 bytes, and the fact that the daemon must broadcast its information in a single packet.
Files
/usr/spool/rwho/whod.* Information about other machines
See Also
rwho(1c), rwhod(8c)
ruptime(1c)