A broken .include link in a unit file will cause 'systemctl
list-unit-files' to simply return 'No such file or directory'. Ignore
this silly error, since we know that the file really does exist.
---
Is there anything that can be done, short of enabling debug level logging, to
make hunting down errors like this a little easier? The bare strerror
messages are pretty useless.
src/install.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/install.c b/src/install.c
index 9256116..30b6911 100644
--- a/src/install.c
+++ b/src/install.c
@@ -1896,7 +1896,7 @@ int unit_file_get_list(
goto found;
r = unit_file_can_install(&paths, root_dir, f->path,
true);
- if (r < 0) {
+ if (r < 0 && r != -ENOENT) {
free(f->path);
free(f);
goto finish;
--
1.7.10
_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
