hpc / hpc/mpifileutils

Running dwalk with --help exits with an error code (1) instead of 0

Open Beginner friendly
#659 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
200
Forks
85
Avg merge
3d 21h
Merged PRs (30d)
2

Description

If you actually ask for --help with dwalk it returns an error instead of success.

root@40ba26226d78:/mfu# dwalk --help; echo $?

Usage: dwalk [options] <path> ...

Options:
  -i, --input <file>      - read list from file
  -o, --output <file>     - write processed list to file in binary format
  -t, --text              - use with -o; write processed list to file in ascii format
  -l, --lite              - walk file system without stat
  -s, --sort <fields>     - sort output by comma-delimited fields
  -d, --distribution <field>:<separators> 
                          - print distribution by field
  -f, --file_histogram    - print default size distribution of items
  -p, --print             - print files to screen
      --no-atime          - use with -l; do not update the file last access time
  -L, --dereference       - follow symbolic links
      --progress <N>      - print progress every N seconds
  -v, --verbose           - verbose output
  -q, --quiet             - quiet output
  -h, --help              - print usage

Fields: name,user,group,uid,gid,atime,mtime,ctime,size
For more information see https://mpifileutils.readthedocs.io. 

1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the dwalk command-line entry point and trace the --help option handling. Run dwalk --help; echo $? before and after the change. Done means the usage text still appears and the command exits with status 0.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
cli
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.