Bug #4380
closed
syslogd missing from Service Watchdog
0%
Description
No idea why it's not there. Certainly would be nice to have it when things go wrong, such as Bug #4352 or https://forum.pfsense.org/index.php?topic=88180.0
Updated by Jim Pingle almost 10 years ago
- Status changed from New to Rejected
It uses the service list provided by the firewall. Same as Status > Services. Adding a service just to the package would be a hack, needs to be added to the base system as a proper service eventually.
Unrelated, but if syslogd is dying, reset the log files, probably one of them is corrupted.
Updated by Kill Bill almost 10 years ago
Kinda don't get why is this rejected. (Oh, and please, don't get me started with "delete the logs", not interested in Lennartware "solutions". :-P)
Updated by Jim Pingle almost 10 years ago
It was rejected because it's not the purpose of this package to track the services itself. The services are defined by the firewall (see /etc/inc/service-utils.inc and /etc/inc/services.inc), and by other packages. This package uses system functions that already exist to manage existing services.
Adding a bunch of new code to show, track, and manage a service that doesn't exist already is outside the scope of this package.
If/when syslogd is added in the base system to show up under Status > Services, then it will automatically work with this package.
Updated by Kill Bill almost 10 years ago
Yes, so it's not a problem with the package, but with the base system. Should I file the bug about the same thing under the pfSense product? Kinda, the purpose of filing the bug was to eventually give users a feasible way to restart syslogd when it crashes for whatever reason, not to play games about where's the fault.
Updated by Jim Pingle almost 10 years ago
Not a bug per se but a feature request. You can submit a feature request to add syslogd as a service under Status > Services.