Skip to content

The --quiet option to dfind doesn't supress log output #650

@jprorama

Description

@jprorama

Running dfind --quiet doesn't appear to suppress logging lines as intended. The telemetry data still gets printed to standard output. Therefore capturing output from via the --print predicate includes but the matching entries and the log lines that show progress of dfind.

For example a run like the follwing

srun --mem 8G -n 1 -N 1 mpiexec -n 1 dfind -i data/newlines-dfind.dat --quiet  --print

Will include the following to log lines at the start of the output

[2025-07-22T18:39:10] Reading from input file: data/newlines-dfind.dat
[2025-07-22T18:39:10] Read 5 files in 0.004 seconds (1309.568 files/sec)

The source suggests these lines are MFU_LOG_INFO level and should be suppressed by --quite:

$ grep -r MFU_LOG_INFO src/*| egrep 'Reading from input|Read .* files in'
src/common/mfu_flist_io.c:        MFU_LOG(MFU_LOG_INFO, "Reading from input file: %s", name);
src/common/mfu_flist_io.c:        MFU_LOG(MFU_LOG_INFO, "Read %lu files in %.3lf seconds (%.3lf files/sec)",

The macro MFU_LOG(level, ...) should be skipping these logs because quiet sets mfu_debug_level = MFU_LOG_NONE in dfind.c

mfu_debug_level = MFU_LOG_NONE;

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions