Sponsored Content
Top Forums Programming ftw/nftw -- filesystem tree walk Post 302176611 by odys on Tuesday 18th of March 2008 06:24:13 PM
Old 03-18-2008
I am using Slackware Linux 10.2 / glibc 2.3.5 (PC machine).

From the 'info' documentation:

>`FTW_PHYS'
>While traversing the directory symbolic links are not
>followed. Instead symbolic links are reported using the
>`FTW_SL' value for the type parameter to the callback
>function. If the file referenced by a symbolic link does not
>exist `FTW_SLN' is returned instead.

Therefore I understand with FTW_PHYS I will have FTW_SL or FTW_SLN given correctly, and FTW_F cannot happen for links.
 

8 More Discussions You Might Find Interesting

1. Programming

ftw function

int ftw(const char *path, int(*func)(), int depth); what does the third parameter(depth) mean? the book said that the larger the value of depth, the fewer directories have to be reopened, therefore increasing the speed of the call. how so? thanks (1 Reply)
Discussion started by: bb00y
1 Replies

2. Programming

using ftw()

hello im trying to find more information about the function: ftw() however it seems every resource has the same thing how to declare it and what it is supposed to do does anyone know of a resource that actually has ftw used within a program, so i can get an idea of how to actually use it?... (0 Replies)
Discussion started by: runawayNinja
0 Replies

3. Programming

find depth using ftw

Hello, I am looking for specific files in my tree directory using ftw(3). How do I know how deep I am in the file structure.. in other words, say I am looking for config.txt files, and my structure looks like this.. /some/directory/user1/config.txt /some/directory/user2/config.txt ....... (2 Replies)
Discussion started by: germallon
2 Replies

4. Shell Programming and Scripting

How to walk through a config file with /bin/sh

Hi there, i tried a lot of things actually to get my script running as expected. Situation: I have a config file with several parameters in the form FFF.thisIsaParam=Value FFF.included.AnotherPortofParam=Value Additionally there are some comments in it. Script should... (8 Replies)
Discussion started by: smhaller
8 Replies

5. UNIX for Dummies Questions & Answers

hwo to find shared filesystem and local filesystem in AIX

Hi, I wanted to find out that in my database server which filesystems are shared storage and which filesystems are local. Like when I use df -k, it shows "filesystem" and "mounted on" but I want to know which one is shared and which one is local. Please tell me the commands which I can run... (2 Replies)
Discussion started by: kamranjalal
2 Replies

6. AIX

Mount Filesystem in AIX Unable to read /etc/filesystem

Dear all, We are facing prolem when we are going to mount AIX filesystem, the system returned the following error 0506-307The AFopen call failed : A file or directory in the path name does not exist. But when we ls filesystems in the /etc/ directory it show -rw-r--r-- 0 root ... (2 Replies)
Discussion started by: m_raheelahmed
2 Replies

7. UNIX for Advanced & Expert Users

"Walk" apache installs and do a tar on them...

Hello unix.com Community: I need help with writing a "common" script that can get the httpd installs by name and install directory|ies and tar.gz them up by name and point that tar operation to the matching install directory. I have 2 Distros that I am concerned with for this task: CentOS and... (3 Replies)
Discussion started by: Habitual
3 Replies

8. HP-UX

SNMP Walk need to enable

We are using a third party to monitor unix servers performance since last 60 days, since last 3 days we are not able to get the performance alarms on our tool. When we check the same with the tool team, they said "SNMP walk is not happening for all the servers." Performance we mean... (9 Replies)
Discussion started by: marunmeera
9 Replies
FTW(3)							     Linux Programmer's Manual							    FTW(3)

NAME
ftw, nftw - file tree walk SYNOPSIS
#include <ftw.h> int ftw(const char *dir, int (*fn)(const char *file, const struct stat *sb, int flag), int depth); int nftw(const char *dir, int (*fn)(const char *file, const struct stat *sb, int flag, struct FTW *s), int depth, int flags); DESCRIPTION
ftw() walks through the directory tree starting from the indicated directory dir. For each found entry in the tree, it calls fn() with the full pathname of the entry, a pointer to the stat(2) structure for the entry and an int flag, which value will be one of the following: FTW_F Item is a normal file FTW_D Item is a directory FTW_DNR Item is a directory which can't be read FTW_SL Item is a symbolic link FTW_NS The stat failed on the item which is not a symbolic link If the item is a symbolic link and stat failed, XPG4v2 states that it is undefined whether FTW_NS or FTW_SL is used. ftw() recursively calls itself for traversing found directories, handling a directory before its files or subdirectories. To avoid using up all a program's file descriptors, the depth specifies the number of simultaneous open directories. When the depth is exceeded, ftw() will become slower because directories have to be closed and reopened. ftw() uses at most one file descriptor for each level in the file hierarchy. To stop the tree walk, fn() returns a non-zero value; this value will become the return value of ftw(). Otherwise, ftw() will continue until it has traversed the entire tree, in which case it will return zero, or until it hits an error other than EACCES (such as a malloc(3) failure), in which case it will return -1. Because ftw() uses dynamic data structures, the only safe way to exit out of a tree walk is to return a non-zero value. To handle inter- rupts, for example, mark that the interrupt occurred and return a non-zero value--don't use longjmp(3) unless the program is going to ter- minate. The function nftw() does precisely the same as ftw(), except that it has one additional argument flags (and calls the supplied function with one more argument). This flags argument is an OR of zero or more of the following flags: FTW_CHDIR If set, do a chdir() to each directory before handling its contents. FTW_DEPTH If set, do a depth-first search, that is, call the function for the directory itself only after handling the contents of the direc- tory and its subdirectories. FTW_MOUNT If set, stay within the same file system. FTW_PHYS If set, do not follow symbolic links. (This is what you want.) If not set, symbolic links are followed, but no file is reported twice. If FTW_PHYS is not set, but FTW_DEPTH is set, then the function fn() is never called for a directory that would be a descendant of itself. The function fn() is called with four arguments: the pathname of the reported entry, a pointer to a struct stat for this entry, an integer describing its type, and a pointer to a struct FTW. The type will be one of the following: FTW_F, FTW_D, FTW_DNR, FTW_SL, FTW_NS (with meaning as above; FTW_SL occurs only with FTW_PHYS set) or FTW_DP Item is a directory and all its descendants have been handled already. (This occurs only with FTW_DEPTH set.) FTW_SLN Item is a symbolic link pointing to a nonexisting file. (This occurs only with FTW_PHYS unset.) The struct FTW pointed at by the fourth argument to fn() has at least the fields base, the offset of the item's filename in the pathname given as first argument of fn(), and level, the depth of the item relative to the starting point (which has depth 0). NOTES
The function nftw() and the use of FTW_SL with ftw() were introduced in XPG4v2. On some systems ftw() will never use FTW_SL, on other systems FTW_SL occurs only for symbolic links that do not point to an existing file, and again on other systems ftw() will use FTW_SL for each symbolic link. For predictable control, use nftw(). Under Linux, libc4 and libc5 and glibc 2.0.6 will use FTW_F for all objects (files, symbolic links, fifos, etc) that can be stat'ed but are not a directory. The function nftw() is available since glibc 2.1. CONFORMING TO
AES, SVID2, SVID3, XPG2, XPG3, XPG4, XPG4v2. SEE ALSO
stat(2) Linux 1999-06-25 FTW(3)
All times are GMT -4. The time now is 07:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy