03-05-2003
It isn't a UFS file system, it's a NIS/NFS auto mount for mounting home directories from a NFS server.
To create a directory in /home, you have to be on the server that is serving out the home directories. Otherwise, if you are looking to create a local account, then create the home directory in /export/home/.
Check out the man page on automount and automountd.
10 More Discussions You Might Find Interesting
1. Programming
I need to compile a file,but 'make' does
not work.please tell me how to use it or
need which tools? (3 Replies)
Discussion started by: dsun5
3 Replies
2. Shell Programming and Scripting
I wonder how I shall read the result below, especially 'what'
shown below.
The result was shown when I entered 'w'.
E.g what is TOP? What is gosh ( what does selmgr mean?)?
login@ idle JCPU PCPU what
6:15am 7:04 39 39 TOP
6:34am 6:45 45 45 TOP
6:41am ... (1 Reply)
Discussion started by: Aelgen
1 Replies
3. Filesystems, Disks and Memory
Hi, guys, I have a big problem.
I've got a sun solaris 4.1.4 workstation, and the /var/adm/message file will add one row every few seconds. It soon becomes a large file.
I wander if there are some mistakes configuring the workstation.
the /var/adm/message is as follow:
... (1 Reply)
Discussion started by: cloudsmell
1 Replies
4. UNIX for Dummies Questions & Answers
echo 'it's friday'
why appear the > (3 Replies)
Discussion started by: yls177
3 Replies
5. UNIX for Advanced & Expert Users
Can someone explain to me why I cannot access or change anything to my solaris /home directory on my sun machine? It has permissions of dr-xr-xr-x so I tried to change them to chmod +w /home, tried chmod 755 /home tried chmod -R 755 home and it always says operation unavailable. And I'm in as... (1 Reply)
Discussion started by: kymberm
1 Replies
6. UNIX for Advanced & Expert Users
Somehow someone created a file named '-ov' in the root directory.
Given the name, the how was probably the result of some cpio command they bozo'ed.
I've tried a number of different ways to get rid of it using * and ? wildcards, '\' escape patterns etc.. They all fail with " illegal option --... (3 Replies)
Discussion started by: GSalisbury
3 Replies
7. Shell Programming and Scripting
Hopefully this doesn't come off as too much of a "newbie" question or a flamebait. But I have recently begun working with a Sun Solaris box after having spent the past five years working with RedHat. From what i can tell, thing look fairly similar and the 'man' command is some help. But I've... (7 Replies)
Discussion started by: deckard
7 Replies
8. Programming
I'm trying to make use of mkdir(char *pathname, S_IRWXU) to create the directories.
but it only creates one directory at a time. so I have to separate the tokens for "/home/blah1/blah2/blah3" as "home blah1 blah2 blah3" using delimiter "/", but it is again hectic to create such directory... (8 Replies)
Discussion started by: platinumedge
8 Replies
9. Shell Programming and Scripting
Is there a way to create a directory in home directory through a bash script?
And if yes then the files we want to put in there have to be put by the time is created in the bash script? (3 Replies)
Discussion started by: vlm
3 Replies
10. Red Hat
for incompatibility installation problems, I've decided to reinstall Centos 6.3
as can be seem from the df output, I've partitioned both / and and /home directories
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda8 12G 5.3G 6.5G 45% /
tmpfs ... (2 Replies)
Discussion started by: jediwannabe
2 Replies
LEARN ABOUT ULTRIX
systemd.automount
SYSTEMD.AUTOMOUNT(5) systemd.automount SYSTEMD.AUTOMOUNT(5)
NAME
systemd.automount - Automount unit configuration
SYNOPSIS
automount.automount
DESCRIPTION
A unit configuration file whose name ends in ".automount" encodes information about a file system automount point controlled and supervised
by systemd.
This man page lists the configuration options specific to this unit type. See systemd.unit(5) for the common options of all unit
configuration files. The common configuration items are configured in the generic [Unit] and [Install] sections. The automount specific
configuration options are configured in the [Automount] section.
Automount units must be named after the automount directories they control. Example: the automount point /home/lennart must be configured
in a unit file home-lennart.automount. For details about the escaping logic used to convert a file system path to a unit name see
systemd.unit(5). Note that automount units cannot be templated, nor is it possible to add multiple names to an automount unit by creating
additional symlinks to its unit file.
For each automount unit file a matching mount unit file (see systemd.mount(5) for details) must exist which is activated when the automount
path is accessed. Example: if an automount unit home-lennart.automount is active and the user accesses /home/lennart the mount unit
home-lennart.mount will be activated.
Automount units may be used to implement on-demand mounting as well as parallelized mounting of file systems.
IMPLICIT DEPENDENCIES
The following dependencies are implicitly added:
o If an automount unit is beneath another mount unit in the file system hierarchy, both a requirement and an ordering dependency between
both units are created automatically.
o An implicit Before= dependency is created between an automount unit and the mount unit it activates.
DEFAULT DEPENDENCIES
The following dependencies are added unless DefaultDependencies=no is set:
o Automount units acquire automatic Before= and Conflicts= on umount.target in order to be stopped during shutdown.
FSTAB
Automount units may either be configured via unit files, or via /etc/fstab (see fstab(5) for details).
For details how systemd parses /etc/fstab see systemd.mount(5).
If an automount point is configured in both /etc/fstab and a unit file, the configuration in the latter takes precedence.
OPTIONS
Automount files must include an [Automount] section, which carries information about the file system automount points it supervises. The
options specific to the [Automount] section of automount units are the following:
Where=
Takes an absolute path of a directory of the automount point. If the automount point does not exist at time that the automount point is
installed, it is created. This string must be reflected in the unit filename. (See above.) This option is mandatory.
DirectoryMode=
Directories of automount points (and any parent directories) are automatically created if needed. This option specifies the file system
access mode used when creating these directories. Takes an access mode in octal notation. Defaults to 0755.
TimeoutIdleSec=
Configures an idle timeout. Once the mount has been idle for the specified time, systemd will attempt to unmount. Takes a unit-less
value in seconds, or a time span value such as "5min 20s". Pass 0 to disable the timeout logic. The timeout is disabled by default.
SEE ALSO
systemd(1), systemctl(1), systemd.unit(5), systemd.mount(5), mount(8), automount(8), systemd.directives(7)
systemd 237 SYSTEMD.AUTOMOUNT(5)