summaryrefslogtreecommitdiff
path: root/net/dhisd
AgeCommit message (Collapse)AuthorFilesLines
2015-12-18Fix previous attempt of passing LDFLAGSwiedi3-9/+30
Ok joerg@
2015-12-13pass along LDFLAGS, still complains about optreset on SunOSwiedi1-2/+2
2015-11-04Add SHA512 digests for distfiles for net categoryagc1-1/+2
Problems found with existing digests: Package haproxy distfile haproxy-1.5.14.tar.gz 159f5beb8fdc6b8059ae51b53dc935d91c0fb51f [recorded] da39a3ee5e6b4b0d3255bfef95601890afd80709 [calculated] Problems found locating distfiles: Package bsddip: missing distfile bsddip-1.02.tar.Z Package citrix_ica: missing distfile citrix_ica-10.6.115659/en.linuxx86.tar.gz Package djbdns: missing distfile djbdns-1.05-test25.diff.bz2 Package djbdns: missing distfile djbdns-cachestats.patch Package djbdns: missing distfile 0002-dnscache-cache-soa-records.patch Package gated: missing distfile gated-3-5-11.tar.gz Package owncloudclient: missing distfile owncloudclient-2.0.2.tar.xz Package poink: missing distfile poink-1.6.tar.gz Package ra-rtsp-proxy: missing distfile rtspd-src-1.0.0.0.tar.gz Package ucspi-ssl: missing distfile ucspi-ssl-0.70-ucspitls-0.1.patch Package waste: missing distfile waste-source.tar.gz Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
2015-03-21Fix rpath use.joerg1-2/+2
2015-03-08(pkgsrc/Makefile)mef7-61/+78
- Add LICENSE= 2-clause-bsd - Drop PKG_DESTDIR_SUPPORT= - Add SUBST_CLASSES to edit Makefile for PREFIX - Add SUBST_CLASSES to edit dhisd.h and README for VARVASE and PREFIX - Add SPECIAL_PERMS to set mode 0700 owner root onto executables (pkgsrc/DESCR) - Add pointer to ${PREFIX}/share/doc/dhisd/README for info (pkgsrc/patches/patch-aa) - Removed (upstream) - Update 5.1 to 5.5 ----------------- On dhisd-5.5 The server no longer requires a 5.4 client to have rport=0 in order to reply to the sending port. This releases a small issue that broke 5.4 clients with servers <= 5.3. As of this version, if the client's version is 5.4 or higher, the server always replies to the sending UDP port and disregards rport. 5.5. clients however continue to fill in rport in order to be compatible with <= 5.3 servers. On dhisd-5.4: The modular architecture has been dropped and the modules and engines are no longer part of dhisd. Instead dhisd is again a DNS only updating daemon without engines; the extra functionality provided by previous engines can however still be replicated with OnCmd and OffCmd scripts on a per-host basis. The default configuration directory is now /usr/local/etc The default binaries directory is now /usr/local/sbin It is now possible to put all configuration parameters under a config file; the default is /usr/local/etc/dhisd.conf The pid file default location moved to /var/run/dhis/dhisd.pid The log file default location moved to /var/log/dhis/dhisd.log The server can now be bound to a specific IP address with either the BindAddr config option or the -b command line option. Multiple options have been added and are now possible with the command line (dhisd -h) and the config file. The server now binds to a UDP port (58800 by default) and sends UDP messages from that port; in previous versions dhisd sent UDP messages from a random port even though it listened on port 58000. In addition to the database text file (specified by the -d option or the DBFile config option), dhisd can now use a MySQL database instead to achieve the same purpose of the dhis.db file. See README and INSTALL for details. This version of the server is compatible with NAT friendly 5.4 clients. On dhisd-5.3: Corrected bug that caused improper handling of comment character (;) in the database file. On dhisd-5.2: Documentation Updates
2014-09-23SunOS needs -lsocket -lnsl.jperkin3-5/+7
2010-03-24Recursive revision bump for GMP update.asau1-1/+2
2009-12-18PKG_DESTDIR_SUPPORTabs1-12/+11
2009-06-14Remove @dirrm entries from PLISTsjoerg1-3/+1
2006-03-04Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where nojlam1-2/+2
developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2005-11-07Pull in libbind resolver on Interix.tv1-0/+11
2005-06-17Create directories before installing files into them.jlam1-1/+2
2005-04-11Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.tv1-2/+1
2005-02-24Add RMD160 digests.agc1-1/+2
2005-02-21Sign over maintainership to tech-pkg@hubertf1-2/+2
2004-12-21Update DHIS server to 5.1, per PR pkg/28704.hubertf3-11/+10
Changes: AUTH_ACK packets return the client's external interface IP address for its possible use.
2004-10-03Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10tv1-2/+2
in the process. (More information on tech-pkg.) Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and installing .la files. Bump PKGREVISION (only) of all packages depending directly on the above via a buildlink3 include.
2004-04-25Convert to buildlink3 and correct two spelling errors in DESCR.snj2-5/+5
2004-01-11Remove inclusion of varargs.h as the program does not appear to usecjep4-10/+20
va_{start,arg,end} and the inclusion stops the program building with gcc3.3. (Also use bl2.)
2003-12-30Add trailing / to HOMEPAGEscjep1-2/+2
2003-07-17s/netbsd.org/NetBSD.org/grant1-2/+2
2002-04-11Improve gmp wildcard to be happy with 4.0.1.wiz1-2/+2
2001-12-05s/root/${ROOT_USER}/g, now that the definition appears in theagc1-2/+2
defs.${OPSYS}.mk files.
2001-10-31Move pkg/ files into package's toplevel directoryzuntum2-1/+1
2001-06-05Import dhisd-5.0: DynDNS serverhubertf6-0/+113
By the means of a DHIS client a host which is assigned a dynamic IP address (either from its ISP or from DHCP) is able to communicate with a DHIS server in order to advertise its newly acquired IP address. The DHIS server (permanently online) listens to UDP messages from its clients and authenticates these against its knowledge of keys. When authentication is successful the DHIS server updates one or more databases with the newly received IP address for the given client. The server then keeps sending, every period of time, check requests to each of its connected clients. These need to be acknowledged. If not the server will consider, on an individual basis, that the client has disconnected and will again update the databases to an offline state. Alternativelly the server may receive an OFFLINE_REQ packet from the client, in which case the DNS record is updated at once and the online state droped.