Free nis software for linux

dnshistory project provide a means for storing a history of DNS and Name changes for the IP Addresses extracted from web log files.
The major target being that multiple analyses of older log files do not require re-lookups of IP Address to FQDNs, and additionally maintain the accuracy of the lookup as it was then and not as it is now.
Main features:
- Do Lookups. The default mode. Given a web log file, dnshistory will perform DNS reverse lookups on each unique IP Address and store the results in a history database.
- Do Translations. Given a raw web log file, dnshistory will make use of a previously created history database and send to STDOUT the same web log but with addresses replaced by the Fully Qualified Domain Name as previously looked up.
- Do Recombining. Given two web log files, one raw and one previously translated (eg. by using dnstran): Create a history database from the values in these separate log files.
- Do Dump. Dump a given history database to STDOUT.
- Show History. Given one or more IP Addresses on the command line, display their history from the database.
Its quite possible that most users would only ever use the first two modes.
The lookups make use of threads for near maximum speed, and use the standard resolution libraries on a system. Thus hosts files, NIS, LDAP and other name resolution methods should work transparently. Unfortunately most other tools ignore local name resolution methods in favour of DNS lookups only.
It is strongly recommended that for massive raw lookups a DNS server is "nearby". Preferably not a forwarding server, or your upstream provider will not like you.
dnshistory can read .gz files. Any input sent via STDIN is currently assumed to not be gz encoded.
dnshistory assumes that the logs being sent are already sorted into oldest --> most_recent date/time order.
A Berkeley Database is used to store the history; as well as possibly reducing the memory footprint within a run.
dnshistory is released under the General Public License.
Enhancements:
- This is practically identical to 1.3-beta1.

Openfiler is a intuitive, powerful browser-based network storage software distribution. Openfiler delivers file-based Network Attached Storage and block-based Storage Area Networking in a single framework.
Openfiler sits atop of CentOS Linux (which is derived from sources freely provided to the public by a prominent North American Enterprise Linux vendor). It is distributed as a stand-alone Linux distribution. The entire software stack interfaces with third-party software that is all open source.
File-based networking protocols supported by Openfiler include: NFS, SMB/CIFS, HTTP/WebDAV and FTP. Network directories supported by Openfiler include NIS, LDAP (with support for SMB/CIFS encrypted passwords), Active Directory (in native and mixed modes) and Hesiod. Authentication protocols include Kerberos 5.
Openfiler includes support for volume-based partitioning, iSCSI (target and initiator), scheduled snapshots, resource quota, and a single unified interface for share management which makes allocating shares for various network file-system protocols a breeze.
Main features:
Powerful block storage virtualization
- Full iSCSI target support, with support for virtual iSCSI targets for optimal division of storage
- Extensive volume and physical storage management support
- Support for large block devices
- Full software RAID management support
- Support for multiple volume groups for optimal storage allocation
- Online volume size and overlying filesystem expansion
- Point-in-time snapshots support with scheduling
- Volume usage reporting
- Synchronous / asynchronous volume migration & replication (manual setup necessary currently)
- iSCSI initiator (manual setup necessary currently)
- Extensive share management features
Support for multiple shares per volume
- Multi-level share directory tree
- Multi-group based access control on a per-share basis
- Multi-host/network based access control on a per-share basis
- Per-share service activation (NFS, SMB/CIFS, HTTP/WebDAV, FTP with read/write controls)
- Support for auto-created SMB home directories
- Support for SMB/CIFS "shadow copy" feature for snapshot volumes
- Support for public/guest shares
- Accounts management
Authentication using Pluggable Authentication Modules, configured from the web-interface
- NIS, LDAP, Hesiod, Active Directory (native and mixed modes), NT4 domain controller
- Guest/public account support
- Quota / resource allocation
Per-volume group-quota management for space and files
- Per-volume user-quota management for space and files
- Per-volume guest-quota management for space and files
- User and group templates support for quota allocation
- Other features
UPS management support
- Built-in SSH client Java applet
- Full industry-standard protocol suite
CIFS/SMB support for Microsoft Windows-based clients
- NFSv3 support for all UNIX clients with support for ACL protocol extensions
- NFSv4 support (testing)
- FTP support
- WebDAV and HTTP 1.1 support
- Linux distribution back-end for any other customizations
- Open source provides you the power to modify and deploy software if you want to do so
Enhancements:
- Updated to kernel 2.6.17. iSCSI CHAP authentication has been added.
- OpenLDAP, Bacula, rsnapshot, and open-iscsi tools have been added.
- Hardware support has been added.
- ATA-Over-Ethernet support (initiator) has been added.
- SUpport for JFS, XFS, and Reiserfs has been added.

libasyncns provides a C library for Linux/Unix for executing name service queries asynchronously. It is an asynchronous wrapper around getaddrinfo and getnameinfo from the libc.
In contrast to GNUs asynchronous name resolving API getaddrinfo_a(), libasyncns does not make use of UNIX signals for reporting completion of name queries. Instead, the API exports a standard UNIX file descriptor which may be integerated cleanly into custom main loops.
In contrast to asynchronous DNS resolving libraries like libdenise, skadns, adns, libasyncns is just an asynchronous wrapper around the libcs synchronous getaddrinfo() API,
which has the adva ntage of allowing name resolution using techniques like Multicast DNS, LDAP or NIS using standard libc NSS (Name Service Switch) modules.
libasyncns is compatible with IPv6 if the underlying libc is.
libasyncns is very tiny, consisting of just one header and one source file. It has no dependencies besides libc.
By default libasyncns spawns a number of worker threads (LWPs) to process name queries. Alternatively or when POSIX Threads are not supported, libasyncns can fork() off worker processes instead.
Installation:
As this package is made with the GNU autotools you should run ./configure inside the distribution directory for configuring the source tree. After that you should run make for compilation and make install (as root) for installation of libasyncns.
Enhancements:
- This version properly detects res_query() on Linux/AMD64 and supports older autoconf versions.

Kronophobia project is a Web-based school calendaring system.
Kronophobia is a complete event-based school calendaring system that supports recurrence, transportation assignments, alerts, parent/public registration, custom reports, event tracking, and e-mail notification.
Main features:
- Event management
- Holiday management
- No School days or Break management
- Event Recurrence and approval system
- Opponent/Schools database for meets,sports games,etc.
- external event Contacts
- organizational system for Campuses, Departments, Activities and Groups
- Transportation integration; including buses, drivers and event assignments
- Facility management; both local and remote
- Equipment organization and checkouts for events
- Custom reporting system with PDF print layouts straight from the web
- User and Group management with complete security customization
- NT, ADS, NIS, etc connectivity through Apache modules for authentication
- User Preference system
- Included Help documentation
- Event tracking and email follow-ups when event changes
- Parent/Visitor sign up system for event tracking
- Record ghosting for obsolete contacts/drivers/etc
- Advanced Filter system for viewing events
- Search capability
- Event alarms to remind participants to show up for events
- Much more...

divine is a utility for laptop users or people who use their machines in different networks all the time. It is meant to be run from the PCMCIA network initialization scripts.
DO NOT make divine setuid root. Divine contains tons of security holes like using system, it is meant as quick hack that will not hurt so much if it is run at boot time.
The idea is this:
- you describe the possible networks in /etc/divine.conf, including one or more machines that are probably up (routers and NIS servers come to mind).
- at boot time, you run divine.
- divine starts a thread that injects fake arp requests into the network. The thread will try again up to three times, pausing 1 second between retries.
If the last try times out again, the thread will print an error message, leave the interface in the original state and exit cleanly.
- the main thread just looks for arp replies and exits if one is found.
- You have one resolv.conf per network, for example /etc/resolv.conf.default and /etc/resolv.conf.work, and divine will symlink one of them to /etc/resolv.conf for you.
- You can specify a proxy server plus port and divine will write the proxy server to /etc/proxy. This can be evaluated inside your shell startup script, like this (zsh):
export http_proxy="http://`< /etc/proxy`/"
The included perl script edit-netscape-proxy.pl will edit the proxy settings in your Netscape 4 preferences file.
- You can even specify an additional script to be run for each selection. You can use this to edit /etc/printcap or /etc/issue or do something else I forgot.

Linux NFS Utilities are NFS utilities for Linux NFS clients and servers.
Main features:
- NFS Versions 2, 3, and 4 are supported on 2.6 and later kernels.
- NFS over UDP and TCP on IPv4 are supported on the latest 2.4 and 2.6 kernels.
- Linux NFS clients and servers have been tested against many non-Linux implementations.
- Since version 1.0.1 of the NFS utilities tarball has changed the server export default to "sync", then, if no behavior is specified in the export list (thus assuming the default behavior), a warning will be generated at export time.
- If you plan to deploy NFS extensively, consider subscribing to one of these mailing lists: NFS Mailing List, or the AutoFS Mailing List. Before reporting problems, you should search for similar issues in the searchable mail archive. Another searchable archive for NFS, supported by Google, is here. The searchable mail archive for AutoFS is here.
- A useful set of generic NFS references includes the following:
- - "NFS Illustrated," by Brent Callaghan; Addison-Wesley, 2000.
- - "Managing NFS and NIS, 2nd edition," by Hal Stern, Mike Eisler, Ricardo Labiaga; OReilly, 2001.
- - "Linux NFS and Automounter Administration," by Erez Zadok; Sybex, 2001.
- - "Using the Linux NFS Client with Network Appliance Filers," by Charles Lever; Netapp TR-3183, 2004.
- - "Mike Eislers NFS blog."
- - "Eric Kustarzs blog."
- - "NFS version 4 home page."
- - Finally, the "linux.org online library" has many references.
Quick setup client guide
1. Acquire and install a recent distribution of Linux.
2. Set up your /etc/exports file (man exports for details).
3. Consult your distributions documentation to determine which /etc/init.d start-up script is used to start your server. Start NFS services by invoking this script as root, using the "start" parameter. Consider adding this script to the list of scripts that are automatically run at system start-up. (Red Hat uses the chkconfig command for this purpose).
4. Read the NFS How-To for advice on tuning and securing your server.
Quick Client Setup Guide
1. Acquire and install a recent distribution of Linux. To enable NLM lock recovery, ensure your clients host name, as returned by uname -n, matches the host name returned by DNS.
2. The NLM protocol is handled by an in-kernel service in modern kernels, but the user-level rpc.statd program must be running to enable NLM lock recovery. Consult your distributions documentation to determine which /etc/init.d start-up script is used to start it. Start the NSM daemon by invoking this script as root, using the "start" parameter. Consider adding this script to the list of scripts that are automatically run at system start-up. (Red Hat uses the chkconfig command for this purpose).
3. Create the directories on your client where you will mount the NFS shares.
4. Add entries in /etc/fstab corresponding to your mount points (man nfs for details).
5. Use mount -a -t nfs to mount the NFS shares.
6. During system boot-up, most distributions automatically mount NFS shares that are listed in /etc/fstab. If yours doesnt, check your distributions documentation for instructions on how to configure your client to do this.
Enhancements:
- The "mount.nfs" command was added, since the nfs mount functionality is being migrated from util-linux to nfs-utils.
- Substantial changes to were made statd. Various pieces of old code were removed.
- Lots of bugfixes and improvements were made.

Mr. LDIF is a python script that builds a seed LDAP authentication database. Its similar to the [PADL] [Migration Tools], except Mr. LDIF has a few key differences:
- Lacks certain features provided by PADLs Migration Tools.
- Written entirely in [python].
- One script with one config file.
- One pass conversion.
- Supports passwd(5), group(5), shadow(5) and Samba v3.
Setup
Mr. LDIF, without any seed files (like the passwd file), will generate a base LDIF that defines the root structure for your LDAP hierarchy. This creates containers for Users, Groups, Samba, and more. There are two steps in providing Mr. LDIF with complete information about your Unix and Samba users.
Gather your flatfile databases.
- Become root.
- Make a copy of your passwd file. It is usually located at /etc/passwd. If you are using - NIS, you will need to use ypcat to get at your passwd file (ypcat passwd). The same goes for group and shadow.
- Make a copy of your group file.
- Make a copy of your shadow file.
- Generate your samba password file by using the utility "pdbedit" (see below)
- Generate your samba account file by using the utility "pdbedit" (see below)
Edit the Mr. LDIF Config file (see below)