Sponsored Content
Top Forums UNIX for Dummies Questions & Answers ls is taking long time to list Post 302717981 by scottaazz on Thursday 18th of October 2012 10:03:55 PM
Old 10-18-2012
The issue you are seeing could also be related to the disk that you are using be setup using "automount" instead of in /etc/fstab.

Take a look at the file "/etc/autofs.conf" (general location to see what is automounted).

Automounted file systems are mapped when accessed and dismounted upon it not being used after a timeout.

Man page for automount:
Code:
 AUTOMOUNT_TIMEOUT
		   The number of seconds after which an automounted file sys-
		   tem will be unmounted if it hasn't been referred to within
		   that period of time.  The default is 10 minutes (600 sec-
		   onds).

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

fetchmail taking long time to fetchmail...

Hi peeps, We are having around 60 users. The time set to retrieve the mail is 300 sec. But it's taking around 1 hour to deliver mails. I am using debian sarge 3.1. any clues? And how it will affect if I decrease the time? My machine has got 1 p4 3.0 GHZ processor and 1 GB ram. The home... (2 Replies)
Discussion started by: squid04
2 Replies

2. Red Hat

login process taking a long time

I'm having a bit of a login performance issue.. wondering if anyone has any ideas where I might look. Here's the scenario... Linux Red Hat ES 4 update 5 regardless of where I login from (ssh or on the text console) after providing the password the system seems to pause for between 30... (4 Replies)
Discussion started by: retlaw
4 Replies

3. Shell Programming and Scripting

For Loop Taking Too Long

I'm new from UNIX scripting. Please help. I have about 10,000 files from the $ROOTDIR/scp/inbox/string1 directory to compare with the 50 files from /$ROOTDIR/output/tma/pnt/bad/string1/ directory and it takes about 2 hours plus to complete the for loop. Is there a better way to re-write the... (5 Replies)
Discussion started by: hanie123
5 Replies

4. Shell Programming and Scripting

<AIX>Problem in purge script, taking very very long time to complete 18.30hrs

Hi, I have here a script which is used to purge older files/directories based on defined purge period. The script consists of 45 find commands, where each command will need to traverse through more than a million directories. Therefore a single find command executes around 22-25 mins... (7 Replies)
Discussion started by: sravicha
7 Replies

5. UNIX for Dummies Questions & Answers

gref -f taking long time for big file

grep -f taking long time to compare for big files, any alternate for fast check I am using grep -f file1 file2 to check - to ckeck dups/common rows prsents. But my files contains file1 contains 5gb and file 2 contains 50 mb and its taking such a long time to compare the files. Do we have any... (10 Replies)
Discussion started by: gkskumar
10 Replies

6. UNIX for Dummies Questions & Answers

Job is taking long time

Hi , We have 20 jobs are scheduled. In that one of our job is taking long time ,it's not completing. If we are not terminating it's running infinity time actually the job completion time is 5 minutes. The job is deleting some records from the table and two insert statements and one select... (7 Replies)
Discussion started by: ajaykumarkona
7 Replies

7. Solaris

How to find out bottleneck if system is taking long time in gzip

Dear All, OS = Solaris 5.10 Hardware Sun Fire T2000 with 1 Ghz quode core We have oracle application 11i with 10g database. When ever i am trying to take cold backup of database with 55GB size its taking long time to finish. As the application is down nobody is using the server at all... (8 Replies)
Discussion started by: yoojamu
8 Replies

8. Shell Programming and Scripting

While loop problem taking too long

while read myhosts do while read discovered do echo "$discovered" done < $LOGFILE | grep -Pi "|" | egrep... (7 Replies)
Discussion started by: SkySmart
7 Replies

9. Shell Programming and Scripting

Long list file display different time format.

Hi Gurus, I have some weird issue. when using ls -l the result shows different time format: -rw-r--r-- 1 abc gourp1 3032605576 Jun 14 2013 abc -rw-rw-r-- 1 abc gourp1 1689948832 Aug 10 06:22 abc one display 2013 which is year; another one displays 06:22 which is time. ... (4 Replies)
Discussion started by: ken6503
4 Replies

10. Shell Programming and Scripting

Rm -rf is taking very long, will it timeout?

I have so many (hundreds of thousands) files and directories within this one specific directory that my "rm -rf" command to delete them has been taking forever. I did this via the SSH, my question is: if my SSH connection times out before rm -rf finishes, will it continue to delete all of those... (5 Replies)
Discussion started by: phpchick
5 Replies
AUTOMOUNT(8)						      System Manager's Manual						      AUTOMOUNT(8)

NAME
automount - manage autofs mount points SYNOPSIS
automount [options] [master_map] DESCRIPTION
The automount program is used to manage mount points for autofs, the inlined Linux automounter. automount works by reading the auto.master(5) map and sets up mount points for each entry in the master map allowing them to be automatically mounted when accessed. The file systems are then automatically umounted after a period of inactivity. OPTIONS
-h, --help Print brief help on program usage. -p, --pid-file Write the pid of the daemon to the specified file. -t <seconds>, --timeout <seconds> Set the global minimum timeout, in seconds, until directories are unmounted. The default is 10 minutes. Setting the timeout to zero disables umounts completely. The internal program default is 10 minutes, but the default installed configuration overrides this and sets the timeout to 5 minutes to be consistent with earlier autofs releases. -n <seconds>, --negative-timeout <seconds> Set the default timeout for caching failed key lookups. The default is 60 seconds. -v, --verbose Enables logging of general status and progress messages for all autofs managed mounts. -d, --debug Enables logging of general status and progress messages as well as debugging messages for all autofs managed mounts. -Dvariable=value, --define variable=value Define a global macro substitution variable. Global definitions are over-ridden macro definitions of the same name specified in mount entries. -f, --foreground Run the daemon in the foreground and log to stderr instead of syslog." -r, --random-multimount-selection Enables the use of ramdom selection when choosing a host from a list of replicated servers. -m, --dumpmaps [<map type> <map name>] With no parameters, list information about the configured automounter maps, then exit. If the dumpmaps option is given and is followed by two parameters, "<map type> <map name>" then simple "<key, value>" pairs that would be read in by a map read are printed to stdout if the given map type and map name are found in the map configuration. If the map is an LDAP map and there is more than one map of same name in different base dns only the first map encountered by autofs will be listed. Similarly, if the map is a file map and there is more than one map of the same name in different directories, only the first map encountered will be listed. If the map type is an old style multi-map and any one of the map names in the multi-map entry matches the given map name the entries that would be used by autofs for the whole multi-map will be listed. -O, --global-options Allows the specification of global mount options used for all master map entries. These options will either replace or be appened to options given in a master map entry depending on the APPEND_OPTIONS configuration setting. -V, --version Display the version number, then exit. -l, --set-log-priority priority path [path,...] Set the daemon log priority to the specified value. Valid values include the numbers 0-7, or the strings emerg, alert, crit, err, warning, notice, info, or debug. Log level debug will log everything, log levels info, warn (or warning), or notice with enable the daemon verbose logging. Any other level will set basic logging. Note that enabling debug or verbose logging in the autofs global configuration will override dynamic log level changes. For example, if verbose logging is set in the configuration then attempting to set logging to basic logging, by using alert, crit, err or emerg won't stop the verbose logging. However, setting logging to de- bug will lead to everything (debug logging) being logged witch can then also be disabled, returning the daemon to verbose logging. This option can be specified to change the logging priority of an already running automount process. The path argument corresponds to the automounted path name as specified in the master map. -C, --dont-check-daemon Don't check if the daemon is currently running (see NOTES). -F, --force Force an unlink umount of existing mounts under autofs managed mount points during startup. This can cause problems for processes with working directories within these mounts (see NOTES). ARGUMENTS
automount takes one optional argument, the name of the master map to use. master_map Location for autofs master map that defines autofs managed mount points and the mount maps they will use. The default is auto.master. NOTES
If the automount daemon catches a USR1 signal, it will umount all currently unused autofs managed mounted file systems and continue running (forced expire). If it catches the TERM signal it will umount all unused autofs managed mounted file systems and exit if there are no re- maining busy file systems. If autofs has been compiled with the option to ignore busy mounts on exit it will exit leaving any busy mounts in place otherwise busy file systems will not be umounted and autofs will not exit. Alternatively, if autofs has been compiled with the option to enable forced shutdown then a USR2 signal to the daemon will cause all mounts to be umounted and any busy mounts to be forcibly umounted, including autofs mount point directories (summary execution). Note that the forced umount is an unlink operation and the actual umount will not happen in the kernel until active file handles are released. The daemon also responds to a HUP signal which triggers an update of the maps for each mount point. If any autofs mount point directories are busy when the daemon is sent an exit signal the daemon will not exit. The exception to this is if autofs has been built with configure options to either ignore busy mounts at exit or force umount at exit. If the ignore busy mounts at ex- it option is used the filesystems will be left in a catatonic (non-functional) state and can be manually umounted when they become unused. If the force umount at exit option is used the filesystems will be umounted but the mount will not be released by the kernel until they are no longer in use by the processes that held them busy. If automount managed filesystems are found mounted when autofs is started they will be recovered unless they are no longer present in the map in which case they need to umounted manually. If the option to disable the check to see if the daemon is already running is used be aware that autofs currently may not function correct- ly for certain types of automount maps. The mounts of the seperate daemons might interfere with one another. The implications of running multiple daemon instances needs to be checked and tested before we can say this is supported. If the option to force an unlink of mounts at startup is used then processes whose working directory is within unlinked automounted direc- tories will not get the correct pwd from the system. This is because, after the mount is unlinked from the mount tree, anything that needs to walk back up the mount tree to construct a path, such as getcwd(2) and the proc filesystem /proc/<pid>/cwd, cannot work because the point from which the path is constructed has been detached from the mount tree. SEE ALSO
autofs(5), autofs(8), auto.master(5), mount(8). autofs_ldap_auth.conf(5) BUGS
Don't know, I've fixed everything I know about. The documentation could be better. Please report other bugs along with a detailed description to <autofs@linux.kernel.org>. For instructions on how to join the list and for archives visit http://linux.kernel.org/mailman/listinfo/autofs AUTHOR
H. Peter Anvin <hpa@transmeta.com> and Ian Kent <raven@themaw.net>. 12 Apr 2006 AUTOMOUNT(8)
All times are GMT -4. The time now is 03:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy