In FreeBSD you can easily let remote hosts log to your system without installing any third party applications. When doing so you might want to separate your remote hosts logs from the local hosts logs which is also easy to do.
Add this to the bottom of your
/etc/syslog.conf on the host accepting the logs:
The trick is
@ which is a handy short for the local hostname, so by negating it like above you get the separation you want.
Works on FreeBSD11.0-Current, check man syslog.conf(5) if this doesn’t work for you.
I have previously been having some issues on my firewall wich I wanted to monitor more closely for, so I use the following script to send me an SMS notice when an error marked as “user.critical” has occured.
I have from time to time seen messages like the following when updating things on my FreeBSD systems
pid 85886 (conftest), uid 0: exited on signal 11 (core dumped)
Since they were pretty sporadic and nothing else was acting up it generally went uninvestigated.
Then a little time ago I updated a load of ports on my web host and the messages just became eerily frequent so I decided to dig into it a bit.
Looking through logs and compile output revealed nothing wrong.
Google to the rescue! I found out that this is actually GNU autoconf forcing this behaviour to make sure the system deals with a segfault correctly.
FreeBSD-questions@ cleared this up years ago, so I guess I should have checked at once and saved myself some worry..
If you let me, that is..
I recently noted that the feed crawler for google reader leaves a note about the number of subscribers to your feed with its requests.
Prior to that I was thinking about trying my way with writing a WordPress plugin, so bingo!
This is basically a pretty lame rewrite of the hello dolly plugin. But somebody else might learn something from my mistakes while I toy around a bit with this..
For now you can download it here. I might put it up on the WordPress plugin site later.
That is if I get around to write an admin page where you can specify wich log file to read and so on..
Right now all it does is display the subscriber count in the admin header from the default apache log.
Go ahead, give it a spin!
Fun fact of the day, Google is kind enough to include the number of subscribed readers each time their feed fetcher polls your feeds.
188.8.131.52 - - [10/Jun/2010:22:37:47 +0200] "GET /feed/ HTTP/1.1" 304 - "-" "Feedfetcher-Google; (+http://www.google.com/feedfetcher.html; 5 subscribers; feed-id=3719683273676272306)"
That makes it easy to check how many subscribers you have to a certain feed.
The feed-id is a 64 bit identifier for the URL of the feed, so if your feed can be accessed via multiple URLs you might see multiple values in you logs. Go sum them up!