|Main index||Section 8||日本語||한국인||Options|
The hlfsd utility is a daemon which implements a file system containing a symbolic link to subdirectory within a user's home directory, depending on the user which accessed that link. It was primarily designed to redirect incoming mail to users' home directories, so that it can read from anywhere.
The hlfsd utility operates by mounting itself as an NFS server for the directory containing linkname, which defaults to /hlfs/home. Lookups within that directory are handled by hlfsd, which uses the password map to determine how to resolve the lookup. The directory will be created if it does not already exist. The symbolic link will be to the accessing user's home directory, with subdir appended to it. If not specified, subdir defaults to .hlfsdir. This directory will also be created if it does not already exist.
A SIGTERM sent to hlfsd will cause it to shutdown. A SIGHUP will flush the internal caches, and reload the password map. It will also close and reopen the log file, to enable the original log file to be removed or rotated. A SIGUSR1 will cause it to dump its internal table of user IDs and home directories to the file /usr/tmp/hlfsd.dump.XXXXXX.
|Alternate directory. The name of the directory to which the symbolic link returned by hlfsd will point, if it cannot access the home directory of the user. This defaults to /var/hlfs. This directory will be created if it does not exist. It is expected that either users will read these files, or the system administrators will run a script to resend this "lost mail" to its owner.|
|Caching interval. The hlfsd utility will cache the validity of home directories for this interval, in seconds. Entries which have been verified within the last cache-interval seconds will not be verified again, since the operation could be expensive, and the entries are most likely still valid. After the interval has expired, hlfsd will re-verify the validity of the user's home directory, and reset the cache time-counter. The default value for cache-interval is 300 seconds (5 minutes).|
|Force fast startup. This option tells hlfsd to skip startup-time consistency checks such as existence of mount directory, alternate spool directory, symlink to be hidden under the mount directory, their permissions and validity.|
|Set the special group HLFS_GID to group. Programs such as comsat(8), (which access the mailboxes of other users) must be setgid HLFS_GID to work properly. The default group is "hlfs". If no group is provided, and there is no group "hlfs", this feature is disabled.|
|Help. Print a brief help message, and exit.|
|Map-reloading interval. Each reload-interval seconds, hlfsd will reload the password map. The hlfsd utility needs the password map for the UIDs and home directory pathnames. The hlfsd utility schedules a SIGALRM to reload the password maps. A SIGHUP sent to hlfsd will force it to reload the maps immediately. The default value for reload-interval is 900 seconds (15 minutes).|
|Specify a log file to which hlfsd will record events. If logfile is the string "syslog" then the log messages will be sent to the system log daemon by syslog(3), using the LOG_DAEMON facility. This is also the default.|
will not verify the validity of the symbolic link it will be
returning, or that the user's home directory contains
sufficient disk-space for spooling.
This can speed up
at the cost of possibly returning symbolic links to home
directories which are not currently accessible or are full.
validates the symbolic-link in the background.
|Mount options. Mount options which hlfsd will use to mount itself on top of dirname. By default, mount-options is set to "ro". If the system supports symbolic-link caching, default options are set to "ro,nocache".|
|Print PID. Outputs the process ID of hlfsd to standard output where it can be saved into a file.|
|Version. Displays version information to standard error.|
|Specify run-time logging options. The options are a comma separated list chosen from: fatal, error, user, warn, info, map, stats, all.|
|Force hlfsd to run on systems that cannot turn off the NFS attribute-cache. Use of this option on those systems is discouraged, as it may result in loss or mis-delivery of mail. The option is ignored on systems that can turn off the attribute-cache.|
|Select from a variety of debugging options. Prefixing an option with the string "no" reverses the effect of that option. Options are cumulative. The most useful option is "all". Since this option is only used for debugging other options are not documented here. A fuller description is available in the program source. A SIGUSR1 sent to hlfsd will cause it to dump its internal password map to the file /usr/tmp/hlfsd.dump.XXXXXX.|
|Read the user-name, user-id, and home directory information from the file password-file. Normally, hlfsd will use getpwent(3) to read the password database. This option allows you to override the default database, and is useful if you want to map users' mail files to a directory other than their home directory. Only the username, uid, and home-directory fields of the file password-file are read and checked. All other fields are ignored. The file password-file must otherwise be compliant with Unix System 7 colon-delimited format passwd(5).|
|/hlfs||directory under which hlfsd mounts itself and manages the symbolic link home.|
|.hlfsdir||default sub-directory in the user's home directory, to which the home symbolic link returned by hlfsd points.|
|directory to which home symbolic link returned by hlfsd points if it is unable to verify the that user's home directory is accessible.|
Proc. LISA-VII, The 7th Usenix System Administration Conference, HLFSD: Delivering Email to Your $HOME, November 1993.
"am-utils" info(1) entry.
Linux NFS and Automounter Administration, ISBN 0-7821-2739-8, Sybex, 2001.,
Alexander Dupuy <email@example.com>, System Management ARTS, White Plains, New York, USA.
Other authors and contributors to am-utils are listed in the AUTHORS file distributed with am-utils.
|HLFSD (8)||February 26, 2016|
|Main index||Section 8||日本語||한국인||Options|
Please direct any comments about this manual page service to Ben Bullock.
|“|| Never write it in C if you can do it in `awk';
Never do it in `awk' if `sed' can handle it;
Never use `sed' when `tr' can do the job;
Never invoke `tr' when `cat' is sufficient;
Avoid using `cat' whenever possible.
|— Taylor's Laws of Programming|