12-20-2017
Hi,
As "vbe" and myself have already said, track down the machine/user combination at "10.61.1.55" - if this is not a machine on your LAN/WAN it is some kind of intrusion.
If it is on your network find out what it's function is, even if you resolve any local issues with your HPUX system locally - it is likely that they will return if this machine carries on doing what it is doing.
Regards
Gull04
Last edited by gull04; 12-20-2017 at 05:18 AM..
Reason: Spelling Correction
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
rwho(1) General Commands Manual rwho(1)
NAME
rwho - show who is logged in on local machines
SYNOPSIS
DESCRIPTION
produces output similar to the output of the HP-UX command for all machines on the local network that are running the daemon (see who(1)
and rwhod(1M)). If has not received a report from a machine for 11 minutes, assumes the machine is down and does not report users last
known to be logged into that machine.
output line has fields for the name of the user, the name of the machine, the user's terminal line, the time the user logged in, and the
amount of time the user has been idle. Idle time is shown as:
If a user has not typed to the system for a minute or more, reports this as idle time. If a user has not typed to the system for an hour
or more, the user is omitted from output unless the flag is given.
An example output line from would look similar to:
This output line could be interpreted as is logged into and his terminal line is has been logged on since September 12 at 13:28 (1:28
p.m.). has not typed anything into for 11 minutes.
WARNINGS
output becomes unwieldy when the number of users for each machine on the local network running becomes large. One line of output occurs
for each user on each machine on the local network that is running
AUTHOR
was developed by the University of California, Berkeley.
FILES
Information about other machines.
SEE ALSO
ruptime(1), rusers(1), rwhod(1M).
rwho(1)