Hello folks... have a problem here hopefully can find some direction with... we have a network using NIS authentication and automount for home dirs and other shared resources. Recently migrated some of our shares off of an EMC Celerra to an Openfiler solution. All of the clients in the NIS domain were perfectly fine with the change, except the AIX. Now, the AIX systems simply don't automount the NFS shares from the Openfiler on demand. I can however mount the NFS shares by hand (as root), but when I do that, it seems that the automountd starts counting down and then unmounts the fs after 10 mins idle. Next time a regular user goes to access, the share is not there. We still have some shares on our EMC Celerras, and those are working fine on the AIX boxes... I don't want to ramble too much here so to the point:
Where are the config files for NIS clients and autofs clients? I can look/modify using smit but I'd like to see the actual files! (been doing unix for years but not much AIX).
I have a hunch there is some kind of bug and/or compatibilty issue with AIX 6.1 and Openfiler. (in fact we do have this working ok on an AIX 5.1 box)
Hello,
I have a CentOS 6.1 server exporting a filesystem with read/write to world. I have an AIX Client mouting this filesystem from an NIS map. One of our applications is giving an error and after a little research, we found that we need the AIX Client to mount this filesystem with NFS V2 for... (6 Replies)
Hi
I am using SUSE 11 linux
I have couple of "nfs" entries in /etc/fstab which are automatically loaded after system restart.
One of the entry is windows drive mounted using cifs as shown below
//IP-Address/Partition /mnt/x cifs credentials=/creds/.creds,rw,uid=<name> 0 0
I want to... (1 Reply)
Hi Admins,
I am new to AIX, pls help me on my below doubts
1) I have received below alerts
Orange : PORTAL detected Filesystem (/nfs/sources) is 92.07% Utilized
Here Orange is server name.
When i did df -k in orange i do not see /nfs/sources filesystem in output.
Doubts
1) how to... (2 Replies)
Folks,
I hope you can help me. I am automounting a filesystem shared from a NAS.
I can create files on the nas, and delete them.
When I go to compress with gzip the command failed saying "Not owner".
Compressing the file with 'compress' works but still gives the same error.
I can't... (4 Replies)
Hi,
I want to print from AIX 5.3/6.1 using 'pr' preprocessing filter and 'PCL' print file type.
Steps:
1. Smitty
2. Print Spooling
3. Create a print queue(remote->Generic)
4. change the attributes for that print queue.
5. Change print file type to PCL and... (1 Reply)
Dear Frndz,
I have a problem in automount.
please find the config file entry for automount /etc/auto_master
/- /mount.map
I have specified all the mappings in /mount.map
The service is operative.
But when i cd into the directory it is not mounting with the server.
Could you... (6 Replies)
We are planning to move to AIX 5.3 and we would like to know if someone has had any 'bad' experiences with it.
We have a 32PE p690 Regatta and currently we are running the latest AIX 5.2 with the latest patches. Has anyone any interesting points to mention when transitioning to AXI 5.3?
Is... (1 Reply)
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 237SYSTEMD.AUTOMOUNT(5)