12-22-2009
It looks like the server is still waiting on something.
Do you have root access on the client machine? If so, you might try dumping all the network traffic to a file (tcpdump) and then connect via rlogin and view the dump file to see what is actually being sent.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
In my system , all user login are via telnet , we have control that only allow max. 300
telnet session in the system , now if I want to keep the max. no of telnet unchange (300) ,
but three specific users ( eg. userA , userB ,userC ) not count into this 300 session , is
it possible ?
for... (0 Replies)
Discussion started by: ust
0 Replies
2. UNIX for Advanced & Expert Users
Hi,
I am very new to Control-M . If anywone know about the global conditions in Control-M. (5 Replies)
Discussion started by: oraclenerd
5 Replies
3. UNIX for Dummies Questions & Answers
Sun 5.8
Though I'd like to be using SSH, my client refuses to do so. So, I'm forced to use rsh/rexec for remote commands. My question is....when running a remote command via "rsh hostname <command>", do I need to have rexecd running, or just rshd on the remote server?
Thanks in advance for... (1 Reply)
Discussion started by: jalburger
1 Replies
4. Shell Programming and Scripting
Need to replace any control character in the string in perl
---------- Post updated at 04:22 PM ---------- Previous update was at 03:50 PM ----------
Any help !!!
Thanks in advance (2 Replies)
Discussion started by: hansini
2 Replies
5. AIX
I am getting an error from one node in a set with RSH setup between them, node one will connect to node two every other time (consistently), however node to connects to node one every time without problem. Here is what I am seeing, makes no sense to me. Can anyone help?
sbhcprdb01<root>: rsh... (6 Replies)
Discussion started by: JodyTek
6 Replies
6. AIX
I am trying to run niminv on my nim master to collect info from my nim clients.
: / -> niminv -o invcon -a targets=<nimclient> -a location=/tmp/inventory
rshd: 0826-813 Permission is denied.
geninv: 0645-007 ATTENTION: gi_nim_standalone() returned an unexpected result.
Return Status: FAILURE... (4 Replies)
Discussion started by: nerradr
4 Replies
7. AIX
Guy's
I have two servers .. server1 and server2
I have configured the rshd and started the rshd demean in both servers by the below command .
startsrc -t shell
lssrc -t shell
Service Command Description Status
shell /usr/sbin/rshd rshd ... (4 Replies)
Discussion started by: Mr.AIX
4 Replies
8. Shell Programming and Scripting
continuing from my previous post, whose link is given below as a reference
https://www.unix.com/shell-programming-scripting/171076-shell-scripting.html#post302573569
consider there is create table commands in a file for eg:
CREATE TABLE `Blahblahblah` (
`id` int(11) NOT NULL... (2 Replies)
Discussion started by: vivek d r
2 Replies
9. Shell Programming and Scripting
here is what i want to achieve... consider a file contains below contents. the file size is large about 60mb
cat dump.sql
INSERT INTO `table1` (`id`, `action`, `date`, `descrip`, `lastModified`) VALUES (1,'Change','2011-05-05 00:00:00','Account Updated','2012-02-10... (10 Replies)
Discussion started by: vivek d r
10 Replies
10. SCO
I would like to log requests to rshd on OSR 5.0.7, hopefully it is possible.
Requests are coming from client Windows PCs, it all works most of the time, but few PCs are not able to do it.
I am not sure where to start - do I tweak syslog.conf? Any pointers would be appreciated. (4 Replies)
Discussion started by: migurus
4 Replies
LEARN ABOUT REDHAT
netdump-server
NETDUMP-SERVER(8) System Programs NETDUMP-SERVER(8)
NAME
netdump-server - handle crash dumps over the network
SYNOPSIS
netdump-server [--port portnumber]
[--concurrent number]
[--pidfile path]
[--daemon]
[--help] [--usage]
DESCRIPTION
Listens to the network for clients that crashes and uses the netdump protocol to recieve a memory dump and a stack trace. The memory dump
and oops message are stored in a timestamped directory in /var/crash. The server can also run scripts when some events happen.
OPTIONS
--port portnumber
Specifies the IP port number for the netdump server to listen to. The default is 6666.
--concurrent number
You can limit the amount of concurrent dumps being done at any one time. If more clients than the specified maximum connects at one
time the last ones will just be logged and then rebooted.
--pidfile path
Store a pidfile. The default service uses /var/run/ttywatch.pid. The default is not to write a pidfile.
--daemon
ttywatch should background itself and run as a daemon.
EXAMPLES
netdump-server --daemon
This launches the netdump-server and puts it in the background, listening for crashed clients.
EXIT STATUS
Exit status is 0 for a clean exit and non-0 for a non-clean exit.
FILES
/etc/netdump.conf
A configuration file read by netdump-server on startup. It is a "key=value" style file. Currently it supports the options: port,
max_concurrent_dumps, daemon and pidfile.
/etc/init.d/netdump-server
An init script to start a default system installation of netdump-server. This is normally turned off by default; use the command
/sbin/chkconfig netdump-server on
to enable the netdump-server service.
/var/crash
The main directory where the crash dump files are stored. Each dump is put in a subdirectory named with the ip of the crashed
machine and the date and time of the crash.
/var/crash/scripts
This directory can contain scripts that are run at various times. They all get passed the ip of the crashing machine as the first
argument, and each one except netdump-start gets the directory that the dump is written into as the second argument.
netdump-start - This is called when a client connects to the server to tell it that it has just started the netdump client. This
normally means that the machine just booted up.
netdump-crash - This is run when a client reports that it has crashed. If it returns a non-zero value the dump request will be
ignored and the client will be told to reboot immediately
netdump-nospace - This is run when there is not enough diskspace for the dump of the crashed machine. If this script exits with a
non-zero return value netdump-server will try once again (but only once) before giving up the dump. If this script exits with a zero
return value, netdump-server will reboot the client without performing a dump.
netdump-reboot - This is run when netdump-server is finished with a client and is about to tell the client to reboot itself.
SEE ALSO
netdump(8)
BUGS
Report any bugs you find to http://bugzilla.redhat.com/bugzilla
AUTHOR
Alexander Larsson <alexl@redhat.com>
Linux 14 Feb 2002 NETDUMP-SERVER(8)