| What | Removed | Added |
|---|---|---|
| Found By | --- | Community User |
What kind of information is missing to resolve this bug by simply correcting the path in the systemd service file or moving lsyncd.conf to the location mentioned in /usr/lib/systemd/system/lsyncd.service? I have absolutely no idea, what has been keeping this kind of bug - with an obvious, already known solution - unfixed for months ...