06-24-2009
Thanks Incredible. Trying a different cable was the first thing tried, then a different port, with no success. After seeing the ip conflict message and fixing the reserved ip address, the server was restarted prior to changing anything else. It did not fix the problem. Then I only changed the IP address and its now changed back. The behaviour is still identical to what it was before. The messages file does not complain about an ip conflict since that was fixed. So I haven't actually isolated teh problem yet, though it may have been triggerred by the ip conflict.
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
MERGE(1) General Commands Manual MERGE(1)
NAME
merge - three-way file merge
SYNOPSIS
merge [ options ] file1 file2 file3
DESCRIPTION
merge incorporates all changes that lead from file2 to file3 into file1. The result ordinarily goes into file1. merge is useful for com-
bining separate changes to an original. Suppose file2 is the original, and both file1 and file3 are modifications of file2. Then merge
combines both changes.
A conflict occurs if both file1 and file3 have changes in a common segment of lines. If a conflict is found, merge normally outputs a
warning and brackets the conflict with and lines. A typical conflict will look like this:
file A
lines in file A
=======
lines in file B
file B
If there are conflicts, the user should edit the result and delete one of the alternatives.
OPTIONS
-A Output conflicts using the -A style of diff3(1), if supported by diff3. This merges all changes leading from file2 to file3 into
file1, and generates the most verbose output.
-E, -e These options specify conflict styles that generate less information than -A. See diff3(1) for details. The default is -E. With
-e, merge does not warn about conflicts.
-L label
This option may be given up to three times, and specifies labels to be used in place of the corresponding file names in conflict
reports. That is, merge -L x -L y -L z a b c generates output that looks like it came from files x, y and z instead of from files
a, b and c.
-p Send results to standard output instead of overwriting file1.
-q Quiet; do not warn about conflicts.
-V Print version number.
DIAGNOSTICS
Exit status is 0 for no conflicts, 1 for some conflicts, 2 for trouble.
IDENTIFICATION
Author: Walter F. Tichy.
Manual Page Revision: ; Release Date: .
Copyright (C) 1982, 1988, 1989 Walter F. Tichy.
Copyright (C) 1990, 1991, 1992, 1993, 1994, 1995 Paul Eggert.
SEE ALSO
diff3(1), diff(1), rcsmerge(1), co(1).
BUGS
It normally does not make sense to merge binary files as if they were text, but merge tries to do it anyway.
GNU MERGE(1)