dist/doc/am-utils.texi

203 The @i{Am-utils} home page is located in
484 coherent set of files such as a user's home directory or a @TeX{}
921 in this case causing the @file{amd.home} map to be rebuilt:
923 $(YPTSDIR)/amd.home.time: $(ETCDIR)/amd.home
924     -@@sed -e "s/#.*$$//" -e "/^$$/d" $(ETCDIR)/amd.home | \
936     $(MAKEDBM) - $(YPDBDIR)/amd.home; \
937     touch $(YPTSDIR)/amd.home.time; \
938     echo "updated amd.home"; \
940         $(YPPUSH) amd.home; \
941         echo "pushed amd.home"; \
983 jsp.homes.automount HS TXT "rfs:=/home/charm;rhost:=charm;sublink:=jsp"
984 njw.homes.automount HS TXT "rfs:=/home/dylan/dk2;rhost:=dylan;sublink:=njw"
999 name in the password file and re-arrange the home directory field to
1002 @i{Amd} assumes the home directory has the format
1013 /home/achilles/jsp
1019 rfs:=/home/achilles;rhost:=achilles;sublink:=jsp
1025 /home/cc/sugar/mjh
1031 rfs:=/home/sugar;rhost:=sugar.cc;sublink:=mhj
1061 For example, an @i{Amd} map @samp{amd.home} that looks as follows:
1074 $ amd2ldif amd.home CUCS < amd.home
1080 dn: cn=amdmap amd.home[/defaults], CUCS
1081 cn          : amdmap amd.home[/defaults]
1083 amdmapName  : amd.home
1087 dn: cn=amdmap amd.home[], CUCS
1088 cn          : amdmap amd.home[]
1090 amdmapName  : amd.home
1094 dn: cn=amdmap amd.home[zing], CUCS
1095 cn          : amdmap amd.home[zing]
1097 amdmapName  : amd.home
1162 For example, the following sequence would be checked if @file{home/dylan/dk2} was
1166    home/dylan/dk2
1167    home/dylan/*
1168    home/*
1626 The name being resolved.  For example, if @file{/home} is an automount
1627 point, then accessing @file{/home/foo} would set @code{$@{key@}} to the
1684 @file{/home/foo} in the example above.
1790 reasons of performance, these have a local @file{/home} partition,
1791 while all other clients on the faster network can access a shared home
1796 home/*  netgrp(ppp-hosts);type:=link;fs:=/local/$@{key@} \
2027 path of the requested file; @samp{/home/foo} in the example above
3258 jsp  host!=charm;type:=nfs;rhost:=charm;rfs:=/home/charm;sublink:=jsp
3587 a user's home directory, also available for public ftp.
3590 lofs      type:=lofs;rfs:=/home/ezk/myftpdir;fs:=/usr/ftp/pub/ezk
3788 (auto-mounted) home directory.  Although this may seem rather expensive,
3808 jsp   host==charm;type:=link;fs:=/home/charm;sublink:=jsp
3810 which would return a symbolic link pointing to @file{/home/charm/jsp}.
3996 @samp{/home/dylan/dk2} and @samp{/home/dylan/dk5} respectively.  Since
3997 @samp{/home} is already an automount point, this naming is achieved with
5542 /home        toplvl /usr/local/etc/amd.home   /home
5543 /homes/jsp   nfs    charm:/home/charm         /a/charm/home/charm/jsp
5544 /homes/phjk  nfs    toytown:/home/toytown     /a/toytown/home/toytown/ai/phjk
5665 hesiod.home      /home              toplvl 1 localhost is up
5668 amy:/home/amy    /a/amy/home/amy    nfs    5 amy is up
5669 swan:/home/swan  /a/swan/home/swan  nfs    0 swan is up (Permission denied)
5670 ex:/home/ex      /a/ex/home/ex      nfs    0 ex is down
6247                 volname /home/dylan/dk2
6258                 volname /home/dylan/dk3
6269                 volname /home/dylan/dk5
6537 A @dfn{map} is typically a tree of filesystems, for example @file{home}
6575     njw -> /home/dylan/njw
6583     njw = /home/dylan/njw
6588 a link will be created leading to @file{/home/dylan/njw} and the
6593 njw type:=link;fs:=/home/dylan/njw
6597 to be in the filesystem @file{/home/dylan} which has previously been
6601 njw rhost:=dylan;rfs:=/home/dylan;sublink:=njw
6984 symbolic link to subdirectory within a user's home directory, depending
6986 redirect incoming mail to users' home directories, so that it can be read
6996 containing @i{linkname}, which defaults to @file{/hlfs/home}.  Lookups
7000 the accessing user's home directory, with @i{subdir} appended to it.  If
7008 dump its internal table of user IDs and home directories to the file
7031 into a designated ``home'' machine, where their mailbox files reside.
7039 to read mail on those machines.  (No home directories were located on
7041 users' home directories to have to compete with CPU-intensive jobs.  At the
7043 their home machines.)
7065 System}, to provide the ability to deliver mail to users' home
7076 to a subdirectory of the invoking user's home directory, and named symbolic
7080 accessing its mount point, and resolves the pathname component @samp{home} as a
7081 symbolic link to a subdirectory within the home directory given by the
7088 or home directory filesystems that are inaccessible or full.
7094 called @samp{home}, pointing to a subdirectory of the user's home directory.
7096 @file{/mail/home}, so that accessing @file{/var/spool/mail} actually
7097 causes access to a subdirectory within a user's home directory.
7115 @tab @t{/mail/home/}@i{NAME}
7116 @tab @t{mail}@@ -> @t{/mail/home}
7119 @tab @t{mail/home/}@i{NAME}
7122 @tab @t{home/}@i{NAME}
7124 @item @t{home}@@
7126 @tab @t{home}@@ -> @t{/users/ezk/.mailspool}
7152 for delivering mail to home directories are not as good as the one used
7170 home'' machine of the user. The greatest advantage of this method is
7180 on the network, not just the one designated as their ``mail home''.
7248 home directories, mail delivery to home directories hasn't caught on.
7276 from the normal spool directory to user home directories is not
7317 directly into the users' home directories:
7324 user's home directory.  It speeds up this operation if the two are on
7325 the same filesystem.  If for some reason the user's home directory is
7343 Delivering mail to users' home directories has another advantage ---
7354 mail delivered to users' home directories, users less concerned with
7364 In summary, delivering mail to home directories provides users the
7412 hlfsd -a /var/alt_mail -x all -l /var/log/hlfsd /mail/home .mailspool
7417 into the user's home directory.
7420 that is a symbolic link to @file{/mail/home}.  @file{/mail} is managed
7421 by @i{Hlfsd}, which creates a dynamic symlink named @samp{home},
7423 accessing user's home directory.  This results in mail which normally
7433 ln -s /mail/home /var/mail
7457 link returned by @i{Hlfsd} will point, if it cannot access the home
7464 Caching interval.  @i{Hlfsd} will cache the validity of home directories
7469 validity of the user's home directory, and reset the cache time-counter.
7491 UIDs and home directory pathnames.  @i{Hlfsd} schedules a @samp{SIGALRM} to
7504 it will be returning, or that the user's home directory contains
7506 cost of possibly returning symbolic links to home directories which are
7542 Read the user-name, user-id, and home directory information from the
7546 a directory other than their home directory.  Only the username, uid,
7547 and home-directory fields of the file @var{password-file} are read and
7567 link @file{home}.
7570 default sub-directory in the user's home directory, to which the
7571 @file{home} symbolic link returned by @i{Hlfsd} points.
7574 directory to which @file{home} symbolic link returned by @i{Hlfsd}
7575 points if it is unable to verify the that user's home directory is
7671 home                  earth:/home
7687 home \
7688   host==earth;type:=link;fs:=/home \\
7689   rhost:=earth;rfs:=/home
7808 redirects mail which cannot be written into the user's home directory to
7903 user home directories may not be accessible across the network.
7980 cross-mounted are those containing user home directories.  A common
7982 @t{/home/}@i{machine}.
7988 @i{machine}:/home/@i{machine} /home/@i{machine} nfs ...
8010 the operator (@samp{opr}) who have a home directory on most machine as
8011 @samp{/home/localhost/opr}.
8015 charm           host!=$@{key@};type:=nfs;rhost:=$@{key@};rfs:=/home/$@{key@} \
8029 dylan/dk2       host!=dylan;type:=nfs;rhost:=dylan;rfs:=/home/$@{key@} \
8032 dylan/dk5       host!=dylan;type:=nfs;rhost:=dylan;rfs:=/home/$@{key@} \
8036 toytown         host!=$@{key@};type:=nfs;rhost:=$@{key@};rfs:=/home/$@{key@} \
8040 zebedee         host!=$@{key@};type:=nfs;rhost:=$@{key@};rfs:=/home/$@{key@} \
8046 gould/staff     host!=gould;type:=nfs;rhost:=gould;rfs:=/home/$@{key@}
8048 gummo           host!=$@{key@};type:=nfs;rhost:=$@{key@};rfs:=/home/$@{key@}
8057 amd /home amd.home
8068 @cindex Example of mounting home directories
8069 @cindex Mount home directories
8071 One convention for home directories is to locate them in @samp{/homes}
8072 so user @samp{jsp}'s home directory is @samp{/homes/jsp}.  With more
8087 jsp         fs:=/home/charm/jsp
8088 njw         fs:=/home/dylan/dk5/njw
8090 phjk        fs:=/home/toytown/ai/phjk
8091 sjv         fs:=/home/ganymede/sjv
8095 appears pointing to the real location of that user's home directory.  In
8097 pointing to @samp{/home/charm/jsp}.  Of course, @samp{/home} would also
8107 jsp   -sublink:=$@{key@};rfs:=/home/charm \
8118 something like @samp{/a/@dfn{host}/home/@dfn{host}} and
8122 /dev/xy0g /a/charm/home/charm 4.2 rw,nosuid,grpid 1 5
8129 jsp          rhost:=charm;rfs:=/home/charm
8130 njw          rhost:=dylan;rfs:=/home/dylan/dk5
8132 phjk         rhost:=toytown;rfs:=/home/toytown;sublink:=ai/$@{key@}
8133 sjv          rhost:=ganymede;rfs:=/home/ganymede