Sponsored Content
Full Discussion: automount script
Top Forums Shell Programming and Scripting automount script Post 302263783 by Christoph Spohr on Tuesday 2nd of December 2008 01:27:04 PM
Old 12-02-2008
Take a look at you fstab. The option "noauto" explicitly demands
_NOT_ to automount the device. If you want it to be mounted
automatically, change "noauto" to "auto".

Further take a look at

Code:
man mount

Your script cannot work due to the way mount uses the
fstab. If you call mount with a device listed in the fstab,
mount will mount it to the mount point specified in the fstab,
-- that's the use of the fstab -- not to a recently created
folder. So if you want the device mounted according to the fstab
extract the information from the fstab if not you have to give
the information needed on the command line.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

automount

I install an external disk on my sun solaris 8 this went fine and I was able to access all filesystem on the disk. the new disk is mounted on /local then 6 hours later files under /local/files was 1 byte in size at the same time I received the following error message in... (4 Replies)
Discussion started by: hassan2
4 Replies

2. UNIX for Advanced & Expert Users

Automount

My site has a few sun solaris server including out NIS server and NFS server on solaris machines. we also have few suse linux and redhat linux machine. All our home directory is on our NFS server(sun Solaris) and this is automounted through /etc/auto_master and /etc/auto_home this worked fine... (1 Reply)
Discussion started by: hassan2
1 Replies

3. UNIX for Advanced & Expert Users

AutoMount

Hi All How do I do a auto mount to a directory in a different unix server. I am using Solaris. Please advise!! TIA Jana (7 Replies)
Discussion started by: janavenki
7 Replies

4. Solaris

CD automount does not work

Hello, I have a SUN Solaris 9 machine (Sun-Fire-V490). I put a DVD in the reader to install a software. The automount procedure did not work (vold is running) : I have nothing under /cdrom When I try "eject" command I have the answer "No default media available" When I try to mount manually the... (3 Replies)
Discussion started by: aribault
3 Replies

5. UNIX for Dummies Questions & Answers

Automount issue

Folks; I'm mounting a directory on a different SUSE 10 server from my SUSE server fine. using this mount command: # mount 192.168.132.11:/var/local/new /var/local/new this command above works fine but when i added a new line to my "/etc/fstab" to be mounted automatically every time i... (2 Replies)
Discussion started by: Katkota
2 Replies

6. Solaris

Automount in Solaris 10

Hi friends I'm a newbie trying to automount a nfs shared directory. Below is the configuration I'm using FreeBSD machine as NFS server. IP Address - 192.168.1.60 # cat /etc/exports /shared 192.168.1.50 Solaris 10 as NFS client. IP Address - 192.168.1.50 # cat... (1 Reply)
Discussion started by: pankajj
1 Replies

7. AIX

Help on Unconfiguring Automount

Hi All, Please help. I need an advise on how to Unconfigure automount please. Many Thanks. (2 Replies)
Discussion started by: EngnrRG
2 Replies

8. Linux

Automount problem

Hi, Please give step by step how to do automount in linux Thanks, Mani (9 Replies)
Discussion started by: Mani_apr08
9 Replies

9. Red Hat

Automount in RHEL

Hello experts, On my RHEL box when i mount a nfs file system using autofs, the df -t shows the file system as nfs only. For which mounts does it report the filesystem as autofs. ?? I actually want to see the filesystem getting reported as autofs instead of nfs. Pls guide me I... (1 Reply)
Discussion started by: achak01
1 Replies

10. Red Hat

Need help with automount.. is not working!!

When i export the directory where the data really is, i can specify which hosts can mount it. On the remote server i create a mount point directory and then mount it to the source servers directory (that has the data). I need to run my script on Server X , i would login there and type in the... (11 Replies)
Discussion started by: bkilaru
11 Replies
SYSTEMD-FSTAB-GENERATOR(8)				      systemd-fstab-generator					SYSTEMD-FSTAB-GENERATOR(8)

NAME
systemd-fstab-generator - Unit generator for /etc/fstab SYNOPSIS
/lib/systemd/system-generators/systemd-fstab-generator DESCRIPTION
systemd-fstab-generator is a generator that translates /etc/fstab (see fstab(5) for details) into native systemd units early at boot and when configuration of the system manager is reloaded. This will instantiate mount and swap units as necessary. The passno field is treated like a simple boolean, and the ordering information is discarded. However, if the root file system is checked, it is checked before all the other file systems. See systemd.mount(5) and systemd.swap(5) for more information about special /etc/fstab mount options this generator understands. One special topic is handling of symbolic links. Historical init implementations supported symlinks in /etc/fstab. Because mount units will refuse mounts where the target is a symbolic link, this generator will resolve any symlinks as far as possible when processing /etc/fstab in order to enhance backwards compatibility. If a symlink target does not exist at the time that this generator runs, it is assumed that the symlink target is the final target of the mount. systemd-fstab-generator implements systemd.generator(7). KERNEL COMMAND LINE
systemd-fstab-generator understands the following kernel command line parameters: fstab=, rd.fstab= Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any mounts or swap devices configured in /etc/fstab. rd.fstab= is honored only by the initial RAM disk (initrd) while fstab= is honored by both the main system and the initrd. root= Takes the root filesystem to mount in the initrd. root= is honored by the initrd. rootfstype= Takes the root filesystem type that will be passed to the mount command. rootfstype= is honored by the initrd. rootflags= Takes the root filesystem mount options to use. rootflags= is honored by the initrd. mount.usr= Takes the /usr filesystem to be mounted by the initrd. If mount.usrfstype= or mount.usrflags= is set, then mount.usr= will default to the value set in root=. Otherwise, this parameter defaults to the /usr entry found in /etc/fstab on the root filesystem. mount.usr= is honored by the initrd. mount.usrfstype= Takes the /usr filesystem type that will be passed to the mount command. If mount.usr= or mount.usrflags= is set, then mount.usrfstype= will default to the value set in rootfstype=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrfstype= is honored by the initrd. mount.usrflags= Takes the /usr filesystem mount options to use. If mount.usr= or mount.usrfstype= is set, then mount.usrflags= will default to the value set in rootflags=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrflags= is honored by the initrd. systemd.volatile= Controls whether the system shall boot up in volatile mode. Takes a boolean argument or the special value state. If false (the default), this generator makes no changes to the mount tree and the system is booted up in normal mode. If true the generator ensures systemd-volatile-root.service(8) is run as part of the initial RAM disk ("initrd"). This service changes the mount table before transitioning to the host system, so that a volatile memory file system ("tmpfs") is used as root directory, with only /usr mounted into it from the configured root file system, in read-only mode. This way the system operates in fully stateless mode, with all configuration and state reset at boot and lost at shutdown, as /etc and /var will be served from the (initially unpopulated) volatile memory file system. If set to state the generator will leave the root directory mount point unaltered, however will mount a "tmpfs" file system to /var. In this mode the normal system configuration (i.e. the contents of "/etc") is in effect (and may be modified during system runtime), however the system state (i.e. the contents of "/var") is reset at boot and lost at shutdown. Note that in none of these modes the root directory, /etc, /var or any other resources stored in the root file system are physically removed. It's thus safe to boot a system that is normally operated in non-volatile mode temporarily into volatile mode, without losing data. Note that enabling this setting will only work correctly on operating systems that can boot up with only /usr mounted, and are able to automatically populate /etc, and also /var in case of "systemd.volatile=yes". SEE ALSO
systemd(1), fstab(5), systemd.mount(5), systemd.swap(5), systemd-cryptsetup-generator(8), kernel-command-line(7) systemd 237 SYSTEMD-FSTAB-GENERATOR(8)
All times are GMT -4. The time now is 10:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy