License issues roil Linux developer community - GCN.com
License issues roil Linux developer community GCN.com, DC - Jun 15, 2007 ... moves its open-source Solaris operating system - another version of Unix - he'd consider dual-licensing Linux so that the two projects could share code. ...
I am looking to hire a Linux Application developer for my startup. But am having trouble screening for the right skill-set. What should I look for ? And, where do I find these developers who have experience in building applications for Linux?
Best,
E (1 Reply)
Hi All,
I have a XML file : System.xml in which I want to update the license tag with the new data from file licence.xml.
The content of files is in following format:
System.xml:
<?xml version="1.0"?>
<!DOCTYPE Configuration SYSTEM "SystemVariables.dtd">
<usageConfiguration... (2 Replies)
Hi,
I am working as a c++/MFC developer from last 3 years on windows, recently i came across LINUX due to some small involvement in c++ projet @ linux platform. I really found it fascinated and found more challenging rather than developing the applications on windows. I really want to go more... (3 Replies)
Although not strictly about the process of coding in C, this forum seemed the most appropriate for this topic. Apologies if that's not correct.
I have been contacted by one of my developers; they are receiving this error message on our AIX box:
4053: cc EXTRACT.c
1506-507 (W) No licenses... (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
