Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I having issue on execute command "ls -l" hanging for few minutes, Normally this only happen on folder has many files/folder. but now it happen on small files/folder too.
i hope i can find the solution in this forum before i escalate to red hat support.
It could probably be that your 'ls' is tied to a circuitous alias; before you detach it you first make a back up (we don't know what the RH people wanted it to), so back it up:
Code:
alias >> my_aliases.txt
then (I am only assuming it is aliased, as usually it is with most distros), remove the alias to run 'ls' in plain vanilla--
Code:
unalias ls
Exit. Launch. (Terminal.) Check use ls.
Hope that helps.
Note: If this doesn't work check your system for "rootkits"! clean and install a fresh copy of bash.
I having issue on execute command "ls -l" hanging for few minutes, Normally this only happen on folder has many files/folder. but now it happen on small files/folder too.
i hope i can find the solution in this forum before i escalate to red hat support.
Please advise.
Thanks.
Is just 'ls' command take a long time too?
If 'ls' is quick and 'ls -l' is slow - do you by any chance use NIS/NIS++?
Is your NIS server OK?
'ls' command quick print the output. it's has problem with 'ls -l,ls -la & ll' command it's take a couple of minute to print the output.
In that case your problem comes from looking up UIDs to usernames (could involve NIS as suggested by another user).
Do you have full disk in /tmp/ or /var/tmp/ ? This could interfere with caching.
What's in your /etc/nsswitch.conf ?
In that case your problem comes from looking up UIDs to usernames (could involve NIS as suggested by another user).
Do you have full disk in /tmp/ or /var/tmp/ ? This could interfere with caching.
What's in your /etc/nsswitch.conf ?
full disk you mean the capacity for /tmp/ or /var/tmp ?
#
# /etc/nsswitch.conf
#
# An example Name Service Switch config file. This file should be
# sorted with the most-used services at the beginning.
#
# The entry '[NOTFOUND=return]' means that the search for an
# entry should stop if the search in the previous entry turned
# up nothing. Note that if the search failed due to some other reason
# (like no NIS server responding) then the search continues with the
# next entry.
#
# Legal entries are:
#
# nisplus or nis+ Use NIS+ (NIS version 3)
# nis or yp Use NIS (NIS version 2), also called YP
# dns Use DNS (Domain Name Service)
# files Use the local files
# db Use the local database (.db) files
# compat Use NIS on compat mode
# hesiod Use Hesiod for user lookups
# [NOTFOUND=return] Stop searching if not found so far
#
# To use db, put the "db" in front of "files" for entries you want to be
# looked up first in the databases
#
# Example:
#passwd: db files nisplus nis
#shadow: db files nisplus nis
#group: db files nisplus nis
passwd: files nisplus
shadow: files nisplus
group: files nisplus
#hosts: db files nisplus nis dns
hosts: files dns
# Example - obey only what nisplus tells us...
#services: nisplus [NOTFOUND=return] files
#networks: nisplus [NOTFOUND=return] files
#protocols: nisplus [NOTFOUND=return] files
#rpc: nisplus [NOTFOUND=return] files
#ethers: nisplus [NOTFOUND=return] files
#netmasks: nisplus [NOTFOUND=return] files
bootparams: nisplus [NOTFOUND=return] files
ethers: files
netmasks: files
networks: files
protocols: files
rpc: files
services: files
netgroup: nisplus
publickey: nisplus
automount: files nisplus
aliases: files nisplus
i don't know much about NIS. as i said i'm beginner in linux
shows you are likely using nisplus, which is a centralised auth system which means all the file ownerships (user+group) have to be looked up on the central server. http://www.eng.auburn.edu/~rayh/solaris/NIS+_FAQ.html
shows you are likely using nisplus, which is a centralised auth system which means all the file ownerships (user+group) have to be looked up on the central server. http://www.eng.auburn.edu/~rayh/solaris/NIS+_FAQ.html
Distribution: Debian testing 64bit at home, EL5 32/64bit at work.
Posts: 196
Rep:
autofs, usb, nfs mounted file systems
When this happens to me it is usually because the file system has to be mounted or awakened.
* autofs mounted file systems will have this behavior
* NFS mounted file systems, that are mounted but not attached, will have this same behavior
* file systems accessed via USB will also have this behavior
So ... provide the content of this file: /etc/fstab
And ... what directory are you in when you do the 'ls' command? We can tell from /etc/fstab file if the directory if it is a file system mount issue.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.