Bug #4380
closed
- 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.
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)
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.
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.
Not a bug per se but a feature request. You can submit a feature request to add syslogd as a service under Status > Services.
Also available in: Atom
PDF
Updated by 
Updated by Kill Bill