Hi all
I am facing a strange problem.
I am using a sun ultra10 spark machine.
first i took a 20gb IDE hard disk and installed solaris 5.8.
But due to some requirement i have to reinstall the OS but this time solaris 2.6.
and now the hard disk capacity is only showing 8gb.
Where the 12gb... (3 Replies)
Hi,
I work in a production support environment. All our PROD machines SPARC machines and Solaris O/S. I want to know how to find out what the hard disk size, RAM size etc. of our PROD machines. Please let me know if there is any way to find out this (other than from system administrator).
... (2 Replies)
:eek: I use this Solaris to run CMS a call acounting software package for my job. No one could run reports today because it said the this when you logged on
"The following file systems are low, and could adversely affect server performance:
File system /: 99%full"
Can some one please explain... (9 Replies)
hi
I've a fresh installation of SCO 5.0.7 on the IDE hard disk.
For SCSI hard disk I can declare, for example blc disk driver using:
# mkdev hd 0 SCSI-0 0 blc 0but it works for IDE hard disk? (3 Replies)
When we write a programme,we declare variables and compiler allocates memory to them.I want to get access to the physical block number of hard-disk where actually the data is stored by the programme "
Some one help me out... (1 Reply)
When we write a programme,we declare variables and compiler allocates memory to them.I want to get access to the physical block number of hard-disk where actually the data is stored by the programme "
Some one help me out... (3 Replies)
Hi all,
I'm kind of new to programming in Linux & c/c++. I'm currently writing a FileManager using Ubuntu Linux(10.10) for Learning Purposes. I've got started on this project by creating a loopback device to be used as my virtual hard disk. After creating the loop back hard disk and mounting it... (23 Replies)
hi
Has anyone already tried to migrate a hard disk with FreeBSD using recoverdisk? (1 Reply)
Discussion started by: ccc
1 Replies
LEARN ABOUT CENTOS
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).
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.
If an automount point is beneath another mount point in the file system hierarchy, a dependency between both units is created
automatically.
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.
SEE ALSO systemd(1), systemctl(8), systemd.unit(5), systemd.mount(5), mount(8), automount(8), systemd.directives(7)systemd 208SYSTEMD.AUTOMOUNT(5)