Sponsored Content
Full Discussion: ls -l : response time slow
Top Forums UNIX for Advanced & Expert Users ls -l : response time slow Post 32481 by BSeanD on Wednesday 27th of November 2002 04:50:39 AM
Old 11-27-2002
That's an odd one.

What OS are you running? What about your HD, is it fairly old?
When you say there's only 55 files, what are you looking at, what file types are they?
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Response time under packet loss

I am experiencing a problem where under a dial condition I am experiencing packet loss, which is failrly normal, but the response to the packet loss is taking bewteen 6 and 10 seconds. Could someone please advise what the industry standard is on the response time under a packet loss senario. (1 Reply)
Discussion started by: shane
1 Replies

2. UNIX for Advanced & Expert Users

Response time & IO max

in HP-UX how i can measure the response time and how can i find the maximum IO (1 Reply)
Discussion started by: salhoub
1 Replies

3. SCO

Slow cd response

Hi All We have one SCO Server here and it never gives us any trouble. Until Now!! Well its not earth shattering but we have one user who is complaining of a very slow response time when changing to his Home Directory. Other users who have similar profiles are OK. I have su'd to this user and I can... (0 Replies)
Discussion started by: JohnOB
0 Replies

4. IP Networking

Apache mod_proxy +DNS slow response problem

My company has a private network, including a Apache web server (Linux) and some WinXP machines. The web server had been configured to use mod_proxy to connect to window update site via another company proxy server. It works for few years. Recently, some parties had setup a DNS server on the... (2 Replies)
Discussion started by: donaldfung
2 Replies

5. Emergency UNIX and Linux Support

Urgent help - intermittent slow response with client

Hi, My application runs on AIX, and clients complain of 3am slowdowns. This seems to have increased in the recent past. Can someone guide me what are the various things that I need to be looking at on he AIX box, that could be causing slowdowns. Thanks in Advance. (4 Replies)
Discussion started by: ggayathri
4 Replies

6. AIX

Slow FTP response on WAN

Hi All. We are using AIX 5.3 ML9. There is 1 Gig NIC installed on two servers (Primary and Secondary) with Full Duplex Mode. We have scheduled a cronjob to copy the backup from primary to secondary thru FTP on WAN. The total data size is 15 GB and it took 9 Hours and 18 Mins with transfer rate... (6 Replies)
Discussion started by: lodhi1978
6 Replies

7. Post Here to Contact Site Administrators and Moderators

Slow response from website

Hi, I am experiencing slow response of unix.com from past 3-4 days. like- - most of the time the page does not reload instantly (when I do a manual reload from browser) - not able to view graphics. ( displays only text). - when posting into forum, the page gets stuck for considerably long... (6 Replies)
Discussion started by: clx
6 Replies

8. Solaris

slow response on solaris terminal

Solaris terminal responding very slow .. we have recently put a T3 hardware in to production , the applications running are it are perfectly and no complaints from user ..but when i ssh to the server ... the terminal response is very very slow .. it takes 3 seconds to show the character i type ..... (3 Replies)
Discussion started by: skamal4u
3 Replies

9. Shell Programming and Scripting

Processes running response time

Hi All I have been asked to write scripts within our monitoring tool for a vast requirement set. One of the requirements is below: • Lowest, Highest & Average response times of the Documentum process threads serving client requests Essentially they want a view where we can see the... (4 Replies)
Discussion started by: simpsa27
4 Replies
FLS(1)							      General Commands Manual							    FLS(1)

NAME
fls - List file and directory names in a disk image. SYNOPSIS
fls [-adDFlpruvV] [-m mnt ] [-z zone ] [-f fstype ] [-s seconds ] [-i imgtype ] [-o imgoffset ] [-b dev_sector_size] image [images] [ inode ] DESCRIPTION
fls lists the files and directory names in the image and can display file names of recently deleted files for the directory using the given inode. If the inode argument is not given, the inode value for the root directory is used. For example, on an NTFS file system it would be 5 and on a Ext3 file system it would be 2. The arguments are as follows: -a Display the "." and ".." directory entries (by default it does not) -d Display deleted entries only -D Display directory entries only -f fstype The type of file system. Use '-f list' to list the supported file system types. If not given, autodetection methods are used. -F Display file (all non-directory) entries only. -l Display file details in long format. The following contents are displayed: file_type inode file_name mod_time acc_time chg_time cre_time size uid gid -m mnt Display files in time machine format so that a timeline can be created with mactime(1). The string given as mnt will be prepended to the file names as the mounting point (for example /usr). -p Display the full path for each entry. By default it denotes the directory depth on recursive runs with a '+' sign. -r Recursively display directories. This will not follow deleted directories, because it can't. -s seconds The time skew of the original system in seconds. For example, if the original system was 100 seconds slow, this value would be -100. This is only used if -l or -m are given. -i imgtype Identify the type of image file, such as raw or split. Use '-i list' to list the supported types. If not given, autodetection methods are used. -o imgoffset The sector offset where the file system starts in the image. -b dev_sector_size The size, in bytes, of the underlying device sectors. If not given, the value in the image format is used (if it exists) or 512-bytes is assumed. -u Display undeleted entries only -v Verbose output to stderr. -V Display version. -z zone The ASCII string of the time zone of the original system. For example, EST or GMT. These strings must be defined by your operating system and may vary. image [images] One (or more if split) disk or partition images whose format is given with '-i'. Once the inode has been determined, the file can be recovered using icat(1) from The Coroners Toolkit. The amount of information recovered from deleted file entries varies depending on the system. For example, on Linux, a recently deleted file can be easily recovered, while in Solaris not even the inode can be determined. If you just want to find what file name belongs to an inode, it is easier to use ffind(1). EXAMPLES
To get a list of all files and directories in an image use: # fls -r image 2 or just (if no inode is specified, the root directory inode is used): # fls -r image To get the full path of deleted files in a given directory: # fls -d -p image 29 To get the mactime output do: # fls -m /usr/local image 2 If you have a disk image and the file system starts in sector 63, use: # fls -o 63 disk-img.dd If you have a disk image that is split use: # fls -i "split" -o 63 disk-1.dd disk-2.dd disk-3.dd SEE ALSO
ffind(1), icat(1) AUTHOR
Brian Carrier <carrier at sleuthkit dot org> Send documentation updates to <doc-updates at sleuthkit dot org> FLS(1)
All times are GMT -4. The time now is 08:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy