diff options
| author | Olivier Gayot <olivier.gayot@sigexec.com> | 2018-06-20 11:42:59 +0200 |
|---|---|---|
| committer | Olivier Gayot <olivier.gayot@sigexec.com> | 2018-06-20 14:20:17 +0200 |
| commit | c64195d14728aa82e280d022e9f7ceff71cfc6c1 (patch) | |
| tree | c4670a6e9fac2bdf2ea60f9f9fa4e6f7e57cc181 /src/process_runs.c | |
| parent | 95c068358acb303ab01ab8dc372f893aec5fe1b0 (diff) | |
Fix invalid handling of glob() errors on Linux
The manual of glob(3) says that the function returns 0 on successful
completion. Any other integer value should be considered an error, not
only negative integers.
In practice, *BSD systems use negative values but Linux uses positive
integers.
Signed-off-by: Olivier Gayot <olivier.gayot@sigexec.com>
Diffstat (limited to 'src/process_runs.c')
| -rw-r--r-- | src/process_runs.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/process_runs.c b/src/process_runs.c index b5e8f11..da2dba1 100644 --- a/src/process_runs.c +++ b/src/process_runs.c @@ -24,7 +24,7 @@ bool process_runs(const char *path) { static glob_t globbuf; memset(pidbuf, 0, sizeof(pidbuf)); - if (glob(path, GLOB_NOCHECK | GLOB_TILDE, NULL, &globbuf) < 0) + if (glob(path, GLOB_NOCHECK | GLOB_TILDE, NULL, &globbuf) != 0) die("glob() failed\n"); if (globbuf.gl_pathc == 0) { /* No glob matches, the specified path does not contain a wildcard. */ |