All Mac computers running Mac OS X v10.4.11 Tiger, Mac OS X v10.5 Leopard, or Mac OS X v10.6 Snow Leopard can perform a system migration over the network. This gives you more choices and flexibility in migrating your applications and data.
Vim Tips and Tricks
Save and quit
:w => Save
:q => Exit as long as there have been no changes
:q! => Exit and ignore any changes
:wq => Save and Exit.
:x => Exit, saving changes
ZZ => Exit and save changes if any have been made
:10,20w filename => writes the... (34 Replies)
Hello Everyone,
Here I am offereing my Services
Word Posting Content Posting
PDF to excel or word
Image to Ms Word typeing
Document Creation
Video Creation
Any type Copy-Paste
Ads Posting
Article Posting
Manual Directory Submission
PR Submission
Social Bookmarking
Web 2.0 Blogs... (1 Reply)
I'm New to AIX / VIOS
We're doing a FC switch cutover on an ibm device, connected via SAN.
How do I tell if one path to my remote disk is lost? (aix lvm)
How do I tell when my link is down on my HBA port?
Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
4. Post Here to Contact Site Administrators and Moderators
What do you think could we open new top topic with tips and tricks and to show to other users some tricks what do we know like dtrace , new virtual server , how to add new users etc.
This is only suggestion (1 Reply)
MDNSD(8) BSD System Manager's Manual MDNSD(8)NAME
mdnsd -- Multicast and Unicast DNS daemon
SYNOPSIS
mdnsd
DESCRIPTION
mdnsd (also known as mDNSResponder on some systems) is a daemon invoked at boot time to implement Multicast DNS and DNS Service Discovery.
On Mac OS X 10.6 (Snow Leopard), mdnsd is also the system-wide Unicast DNS Resolver.
mdnsd listens on UDP port 5353 for Multicast DNS Query packets. When it receives a query for which it knows an answer, mdnsd issues the
appropriate Multicast DNS Reply packet.
mdnsd also performs Unicast and Multicast DNS Queries on behalf of client processes, and maintains a cache of the replies.
mdnsd has no user-specifiable command-line argument, and users should not run mdnsd manually.
LOGGING
There are several methods with which to examine mdnsd's internal state for debugging and diagnostic purposes. The syslogd(8) logging levels
map as follows:
Error - Error messages
Warning - Client-initiated operations
Notice - Sleep proxy operations
Info - Informational messages
By default, only log level Error is logged.
A SIGUSR1 signal toggles additional logging, with Warning and Notice enabled by default:
# pkill -USR1 mdnsd
A SIGUSR2 signal toggles packet logging:
# pkill -USR2 mdnsd
A SIGINFO signal will dump a snapshot summary of the internal state to /var/log/system.log:
# pkill -INFO mdnsd
FILES
/usr/sbin/mdnsd
SEE ALSO dns-sd(1), pkill(1), syslogd(8)
For information on Multicast DNS, see http://www.multicastdns.org/
For information on DNS Service Discovery, see http://www.dns-sd.org/
For information on how to use the Multicast DNS and the DNS Service Discovery APIs on Mac OS X and other platforms, see
http://developer.apple.com/bonjour/
For the source code to mdnsd, see http://developer.apple.com/darwin/projects/bonjour/
HISTORY
The mdnsd daemon first appeared in Mac OS X 10.2 (Jaguar).
Also available from the Darwin open source repository (though not officially supported by Apple) are mdnsd daemons for other platforms,
including Mac OS 9, Microsoft Windows, Linux, FreeBSD, NetBSD, Solaris, and other POSIX systems.
BUGS
mdnsd bugs are tracked in Apple Radar component "mDNSResponder".
BSD February 27, 2011 BSD
