What about "package logs"
-
Now its a while this entry exists, but ther is not even one package which puts its logs there.
To give only one example: squid.
I have to access pfsense via ssh to see the logs. Thats not very helpful. I don't know who are the respective devs of the packages, but wouldn't it be nice to see any package-log here?
-
That's up to the individual package maintainers, really. I'm not sure any packages actually use it. If there were more examples/documentation of how to tie into it, it might see more use.
-
Yep, thats what i'm thinking too. I was thinking about asking the question in the forum "packages", but due to the fact that its a version 2 question too, i decided asking here.
Unfortunately no package logs there, its only message is "No packages with logging facilities are currently installed.", which in fact is not true.My second thinking was that the maintainers of the packages would look here to see what changes ccur to the respective handling in pfSense 2, so it made the most sense to me.
edit: I think, i will ask the same question in packages.
Much thanks for your answer. -
Looks like that page assumes the packages will log with clog, which none of them do even if they have logs.
It should be easy for a package to specify in its xml where its logs will be stored (or in the case of squid, where it's configurable, it could be determined logically), and then the package logs page could merely display those files. Not sure if clearing them would be possible in a way that would be automatic unless a package included its own function to clear its log. Some will do fine with a -HUP and others require a full restart.
-
hmmm, maybe that could be solved via a cron-job. But in deep only the maintainer can tell us which is the best way to accomply this task.
For the most people it would be great to see that logs without having to switch via ssh into the box and grab all logs in their respective folders, which could be a long task if that logs are stored all over the file-system.
-
You never need ssh to do that if you know where the logs are, you can use Diagnostics > Command, or Diagnostics > Edit File (and the latter can even browse through the filesystem with a GUI)
I wouldn't do the log clearing with a cron job most of the time, only manually, but I suppose that might be a personal preference.
