12-21-2012
Just a first thought. Is the lo interface up?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi, dear all, I am rather new to Unix and have this problem where I cant seem to ping from 1 host to another. The scenerio is as follows: -
1 QNX host->Eth->1 SCO host
the SCO host is configured with it's IP
the QNX host is configured with another IP
both in the same domain, ie, 172.20.3.XX... (3 Replies)
Discussion started by: gavon
3 Replies
2. UNIX for Dummies Questions & Answers
Hello,
hi guys I don't know what is the problem with my NIC I can ping the Localhost (LOOPBACK) but when I run a scripts to check the NIC statuse it's shown the NIC DOWN sooo what could be the problem and what is the best way to start trouplshooting the NIC in SUN-SOLARIS.
Regards,
Karim
... (3 Replies)
Discussion started by: geoquest
3 Replies
3. UNIX for Dummies Questions & Answers
I have Sco openserver 5.0. It had a 125. ip. I changed it to a 192. ip. was unable to ping the 192. I was told to change it in the
etc/tcp
etc/hosts
files which i did. still unable to ping.
i am getting a message unable to route to host.
I also have an error in my etc/tcp file on line... (1 Reply)
Discussion started by: pdoug76
1 Replies
4. UNIX for Dummies Questions & Answers
DEar all
i am receiving this error on start and then unable to ping
(dlpid): unable to open network adapter driver (/dev/mdi/e3h0)
what to do ? (2 Replies)
Discussion started by: sak900354
2 Replies
5. IP Networking
We are unable to bring one of our linux boxes into the network once it was restarted. But once we stop and start the network service. We are able to ping the gateway and get into network. After a minute or two we get the following reponse for the ping command
64 bytes from 124.168.215.40:... (6 Replies)
Discussion started by: chrisanto_2000
6 Replies
6. Solaris
hi,
I setup a Solaris machine in my server room and my client cannot access it. Can anyone advise?
Test that i have done:
-My client pc cannot ping the server.
-My solaris server cannot ping client
-My solaris server can ping it's gateway
-Another NT machine 1 (10.179.30.26) in the server... (2 Replies)
Discussion started by: skiturn
2 Replies
7. IP Networking
hi,
I setup a Solaris machine in my server room and my client cannot access it. Can anyone advise?
Test that i have done:
-My client pc cannot ping the server.
-My solaris server cannot ping client
-My solaris server can ping it's gateway
-Another NT machine 1 (10.179.30.26) in the... (8 Replies)
Discussion started by: skiturn
8 Replies
8. Solaris
Hi ALL,
I Have installed NEW v240 server through hyper terminal, After installation i unable to ping the server from out side server... i can see no entry in resolve.conf file.. but the server has DNS.. willl that issue.. please guide me ping the server from outside within the same network
bk (1 Reply)
Discussion started by: suresh_krish
1 Replies
9. Solaris
Hello,
Am unable to ping the Windows Box, from my Solaris Box.
They both are in same LAN, have the same IP Segments.
Windows IP :: 10.141.14.120
Solaris IP :: 10.141.14.11
Unable to get why isnt working out.... When using the command 'ping 10.141.14.120', it gives the error as 'ping:... (4 Replies)
Discussion started by: jayanto
4 Replies
10. IP Networking
Hello Everyone,
I have unable to run the default server with localhost in my Debian machine. While trying to run Django I get:
Error: That IP address can't be assigned-to.
error
While trying to run galaxy-dist I get this error:
socket.error: Cannot assign requested address
I can't telnet... (3 Replies)
Discussion started by: sachit adhikari
3 Replies
LEARN ABOUT LINUX
ctluser
CTLUSER(8) System Manager's Manual CTLUSER(8)
NAME
ctluser - control lusers
SYNOPSIS
ctluser [ -h ] [ -m ] command [ argument... ]
DESCRIPTION
Ctluser sends a message to the control channel of a given luser(8) This command can only be run by the sysadmin(1)
In the normal mode of behavior, the message is sent to the luser's brain, which then performs the requested action and sends back a reply
with a text message and the exit code for ctluser. If the luser's brain successfully performed the command, ctluser will exit with a sta-
tus of zero and print the reply on standard output.
The ``-m'' flag is used to display an MPEG of the results of the given command on the console of the sysadmin(1) Note that this requires
the sysadmin(1) to be running an X server.
To see a command summary, use the ``-h'' flag. If a command is included when ctluser is invoked with the ``-h'' flag, then only the usage
for that command will be given.
The complete list of commands follows. Note that all commands have a fixed number of arguments. If a parameter can be an empty string,
then it is necessary to specify it as two adjacent quotes, like "".
addhist <entry>
Add an entry to the luser's employment record.
allow reason
Allow a luser to use the computer system again. The reason must be the same text given with an earlier ``reject'' command. Note
that this command is currently not implemented.
begin name
Begin a new luser(1) with the given file. Note that this command is currently not implemented.
cancel pid
Causes a process of a luser to be killed
changegroup group
Changes a luser from their current workgroup to the one specified.
checkfile
Forces a user to return to a paper based system
drop Causes a large mass to drop onto the luser from a great height.
flushlogs
Destorys all logs of the actions done by the sysadmin(1) to the luser.
go reason
The luser is fired for the given reason.
hangup Makes the luser hang themselves
mode Displays the operating mode of the luser
newgroup group
Causes a luser to make their own newgroup up
pause thought
Makes the luser pause for the given thought. Note that this may cause some lusers to crash
shutdown reason
Makes the luser shutdown. This is essentially the same as killing them
signal sig
Sends the given signal to the luser
throttle reason
Causes the luser to throttle themselves
trace item flag
Gives the sysadmin(1) information on what the luser is doing.
BUGS
Ctluser sometimes has the effect of lusers complaining the to management. The use of bosskill(8) maybe required at this point.
HISTORY
Written by Simon Burr <simes@tcp.co.uk>. Based upon the manual page for ctlinnd(8), part of the InterNetNews system.
SEE ALSO
luser(1), sysadmin(1), bosskill(8)
19 October 1995 CTLUSER(8)