06-24-2009
You should not have changed anything on the system. You should have disconnected and reconnect the cable or worst case you should have rebooted the system once since you found out the conflicting IP and isolating it
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Dear Reader,
I have a very unique problem. Quite often my on board ethernet port( hme0 ) related message is appearing in /var/adm/messages.
The message is hme0: babble.. The port is up and alive.
What does this message mean.. Is the on board port is about to fail??
Thanks in advance, (2 Replies)
Discussion started by: joseph_shibu
2 Replies
2. UNIX for Advanced & Expert Users
How do you configure more than one network on a single hme0 interface under SunOS? And why would you want to do this?
Thanx :)
-Michelle (1 Reply)
Discussion started by: Michelle1977
1 Replies
3. BSD
hi
I want to setup my cable modem under OpenBSD. I did not configure my network while installing the system.
When I type, I get
# ifconfig -a
lo0 : ....
...
...
rl0 : ....
...
...
vr0 : ...
...
...
I have two network cards (the machine will be a router).
I created... (1 Reply)
Discussion started by: fnoyan
1 Replies
4. Solaris
Hi all,
Is there any difference between a null modem cable or a modem cable ?
i assume that a null modem cable is a normal cable that i used from cpu serial ports to a modem for dialup.
please correct if i am wrong,
thks (2 Replies)
Discussion started by: waterbear
2 Replies
5. Solaris
Hi .....
My problem is that when i reboot the system i can't connect to the network because my ethernet ( hme0 ) is down , i must up it by ifconfig command
after reboot :
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask... (1 Reply)
Discussion started by: tt155
1 Replies
6. Solaris
I have a 420r server it boots up all of the network settings are correct, however the machines network connection is not working. Cant ping anything from it, cant ping it from another machine on the network.
If I ping 127.0.0.1 it says alive.
Is there a chance the network card has been... (2 Replies)
Discussion started by: alanj4
2 Replies
7. Solaris
Hi All,
1. modify /etc/default/login file as
make commented # console=
2.put my laptops ip at both
/etc/inet/ipnodes and /etc/host file
still i can login via telnet/ftp through a DB9-serial cable, but when i tried
through a lan stratight cable directly connected that machine... (7 Replies)
Discussion started by: mahadib
7 Replies
8. Solaris
Hi all,
really interesting thing I have encountered . So :
root@host4 # uname -a
SunOS host4 5.9 Generic_122300-31 sun4u sparc SUNW,Sun-Fire-880
root@host4 # scinstall -p
3.2
latest recommended patches applied ..all SUN cluster patches applied.
SUN cluster software installed without... (2 Replies)
Discussion started by: samar
2 Replies
9. Solaris
We are unable to ping from Sun Ultra 60 to Ultra 10 machine and vice versa. We are getting an error message Cable Link Down ?. It was working fine.
Troubleshooting steps taken.
1) Changed the IPaddresses on both machines 192.168.10.10 and 192.168.10.20. These machines connected through 8 port... (2 Replies)
Discussion started by: vijaykrishna
2 Replies
10. Red Hat
I am facing strange problem regarding hostname on my Linux(2.6.18-164.el5xen x86_64 GNU/Linux), the hostname changes if reboot with lan cable and with NO lan cable
Reboot with lan cable:
The hostname is ubunut
Unable to connect Oracle database using sqlplus some times database is not... (2 Replies)
Discussion started by: LinuxLearner
2 Replies
LEARN ABOUT CENTOS
oddjobd
oddjobd(8) System Manager's Manual oddjobd(8)
NAME
oddjobd - privileged operations for unprivileged processes
SYNOPSIS
oddjobd [-n] [-d] [-p pidfile] [-c configfile] [-S] [-t timeout]
DESCRIPTION
The oddjobd daemon provides the com.redhat.oddjob service on the system-wide message bus. Each facility which oddjobd provides is provided
as a separate D-Bus method.
Any method can be invoked by name by any user, subject to access controls enforced by both D-Bus and oddjobd.
Most methods are implemented as helper programs.
OPTIONS
-n Do not fork and become a daemon process.
-d Print debugging messages to stderr. Implies -n.
-p pidfile
Store the daemon's process ID in the named file.
-c /etc/oddjobd.conf
Read the daemon's configuration from the named file.
-S Connect to the session bus instead of the system bus. Used for testing only.
-t timeout
Specifies the amount of time which will pass between attempts to reconnect to the bus if oddjobd is disconnected for any reason. If
the specified timeout is above 5, then oddjobd will first attempt to connect up to 10 times at intervals of 5 seconds. The default
reconnect timeout is 30 seconds.
SIGNALS
SIGHUP Reload the configuration. Client requests which are in the process of being served will run to completion even if the newly-loaded
configuration does not include the service, object, interface, or method.
SEE ALSO
oddjob_request(1) oddjob.conf(5) oddjobd.conf(5)
oddjob Manual 5 April 2006 oddjobd(8)