Does readdir() guarantee an order?

CReaddir

C Problem Overview


I'm getting a list of files on a linux-like system using opendir/readdir. It appears that the directory entries are returned in alphabetical order of file name. However, I don't see anything in the man pages about this order being guaranteed.

Can anyone tell me whether or not readdir guarrantees an order?

C Solutions


Solution 1 - C

The readdir method doesn't guarantee any ordering. If you want to ensure they are sorted alphabetically you'll need to do so yourself.

Note: I searched for a bit for definitive documentation saying this is the case. The closest I came is the following link

It's by no means definitive but it does give a nice overview of the command, its history and how its implementation is typically traversal order.

Solution 2 - C

In short, no, readdir() does not guarantee any particular order.

from a readdir example in the https://www.gnu.org/software/libc/manual/html_node/Simple-Directory-Lister.html">glibc manual

> The order in which files appear in a directory tends to be fairly > random. A more useful program would sort the entries (perhaps by > alphabetizing them) before printing them

Solution 3 - C

From "The linux programming interface":

> The filenames returned by readdir() are not in sorted order, but rather in the order in which they happen to occur in the directory (this depends on the order in which the file system adds files to the directory and how it fills gaps in the directory list after files are removed). (The command ls –f lists files in the same unsorted order that they would be retrieved by readdir().) > > We can use the function scandir(3) to retrieve a sorted list of files matching programmer-defined criteria; see the manual page for details. Although not specified in SUSv3, scandir() is provided on most UNIX implementations.

Note: scandir is a part of POSIX.1-2008. A permissibly-copyrighted version defined around readdir is available in FreeBSD libc.

Solution 4 - C

It's explicitly not guaranteed. The ordering often follows some rules, but the rules are complicated enough that you should not rely on them. The ordering may, for example, be affected by other operations happening in the same directory, and you can't control those. Treat the ordering as random, and sort things yourself if you need to.

Solution 5 - C

No, readdir does not guarantee any order.

(Some file systems might store directory entries in a certain order, in such cases readdir might return them to you in the same order, but that's not a feature of readdir itself.)

Solution 6 - C

readdir() does not guarantee any other order above that which is OS disk read order.


According to test which i made on few platforms - Solaris - sun4sol, x86 sol, linux, Windows with the sample code all results were displated in a random manner.


source: https://stackoverflow.com/questions/20265328/c-readdir-beginning-with-a-dots-instead-of-files

#include <stdio.h>
#include <stdlib.h>
#include <dirent.h>

int main() {
    
    DIR *dir;
    struct dirent *dp;
    char * file_name;
    char dirpath [100] ;


    while(1==1){
	    printf("Choose dir:");
	    scanf("%s",dirpath);
        dir = opendir(dirpath);
        while ((dp=readdir(dir)) != NULL) {
            if ( !strcmp(dp->d_name, ".") || !strcmp(dp->d_name, "..") )
            {
                // do nothing (straight logic)
            } else {
                file_name = dp->d_name; // use it
                printf("file_name: \"%s\"\n",file_name);
            }
        }
        closedir(dir);
    }

    return 0;
}

Solution 7 - C

In addition to the other answers, the readdir man page is pretty clear about files ordering.

> The order in which filenames are read by successive calls to readdir() depends on the filesystem implementation; it is unlikely that the names will be sorted in any fashion.

Some file systems, like ReiserFS do list the files in lexical order.

In your case, you have to store the names in an array, then sort the array.

For instance, use qsort() to sort the array.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionTomView Question on Stackoverflow
Solution 1 - CJaredParView Answer on Stackoverflow
Solution 2 - CJoachim IsakssonView Answer on Stackoverflow
Solution 3 - Cefannu-723View Answer on Stackoverflow
Solution 4 - Cuser25148View Answer on Stackoverflow
Solution 5 - CnosView Answer on Stackoverflow
Solution 6 - CWojciech PapajView Answer on Stackoverflow
Solution 7 - CDéjà vuView Answer on Stackoverflow