10-08-2008
Mac OS X 10.5 Server: Preventing DDNS registration for multiple interfaces
When connecting Mac OS X Server version 10.5 to networks that implement dynamic DNS (DDNS), including Microsoft Active Directory networks, Mac OS X Server may register each configured network interface address in DNS. For multi-homed servers, this may cause confusion and prevent clients from connecting to the server.
More from Apple OS X Support ...
8 More Discussions You Might Find Interesting
1. IP Networking
I have a Unix box with 2 network interfaces on the same IP subnet and would like to add a host route via a specific interface. Any assistance would be greatly appreciated. (3 Replies)
Discussion started by: diemos
3 Replies
2. UNIX for Dummies Questions & Answers
I'm having some problems here, and was wondering whether it was an Apache problem. We have two firewalls where I'm at, Apache is installed on the second one. The first firewall is setup to forward all outside requests to port 80 on the second firewall. Apache is only working on the lan, not the... (2 Replies)
Discussion started by: cerberusofhnsg
2 Replies
3. IP Networking
I have an OpenBSD 3.7 firewall with five network interfaces on it, one of which is connected to the Internet. I'd like to use the remaining four interfaces as a network switch for a single internal subnet. The main problem I have is that the DHCP daemon doesn't like multiple interfaces matching... (0 Replies)
Discussion started by: vertigo23
0 Replies
4. AIX
Is there a way to add routes using the add route command in AIX to add different routes and bind them to different NICS installed in the box? (2 Replies)
Discussion started by: Docboyeee
2 Replies
5. 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
6. Shell Programming and Scripting
I've been bitten by using a lock or pid file to prevent multiple instances of a script. A user typed kill -9, and the pid file didn't go away. You can't trap -9. So when he tried to restart, it said "already running", and I got trouble report. Argh.
So here's what we came up with:
# Stop if... (1 Reply)
Discussion started by: McFadden586
1 Replies
7. AIX
Hi .. we have two AIX 5.3 systems with a small client server app communicating over a TCP socket.
Box A has a single network interface where the server app (in Java) opens a well known port and waits for connections from Box B.
Box B has two network interfaces, X and Y. Interface X has the... (4 Replies)
Discussion started by: RonBowater
4 Replies
8. IP Networking
four interfaces with ifconfig
all interfaces have the same mac. If is not set for unique.
but it still works.
what difference does it make to have all macs the same or different? (4 Replies)
Discussion started by: rrodgers
4 Replies
CPMAC(1) BSD General Commands Manual CPMAC(1)
NAME
/usr/bin/CpMac -- copy files preserving metadata and forks
SYNOPSIS
/usr/bin/CpMac [-rp] [-mac] source target
/usr/bin/CpMac [-rp] [-mac] source ... directory
DESCRIPTION
In its first form, the /usr/bin/CpMac utility copies the contents of the file named by the source operand to the destination path named by
the target operand. This form is assumed when the last operand does not name an already existing directory.
In its second form, /usr/bin/CpMac copies each file named by a source operand to a destination directory named by the directory operand. The
destination path for each operand is the pathname produced by the concatenation of the last operand, a slash, and the final pathname compo-
nent of the named file.
The following options are available:
-r If source designates a directory, /usr/bin/CpMac copies the directory and the entire subtree connected at that point. This option also
causes symbolic links to be copied, rather than indirected through, and for /usr/bin/CpMac to create special files rather than copying
them as normal files. Created directories have the same mode as the corresponding source directory, unmodified by the process' umask.
-p Causes /usr/bin/CpMac to preserve in the copy as many of the modification time, access time, file flags, file mode, user ID, and group
ID as allowed by permissions.
-mac Allows use of HFS-style paths for both source and target. Path elements must be separated by colons, and the path must begin with a
volume name or a colon (to designate current directory).
NOTES
The /usr/bin/CpMac command does not support the same options as the POSIX cp command, and is much less flexible in its operands. It cannot
be used as a direct substitute for cp in scripts.
As of Mac OS X 10.4, the cp command preserves metadata and resource forks of files on Extended HFS volumes, so it can be used in place of
CpMac. The /usr/bin/CpMac command will be deprecated in future versions of Mac OS X.
SEE ALSO
cp(1) MvMac(1)
Mac OS X April 12, 2004 Mac OS X