I reflashed card. First error no longer bothers Me! :)

Sencond one is connected with queues. As I said before I've made queues Myself by editing config.xml file, and that's why it appers.

Thanks for help!

You can add cron items directly to the config.xml with the latest snapshots. To see the syntax just open a config.xml of a recent snapshot and have a look at the very bottom.

thanks for this info. very helpful.

Going to try and use php-syslog-ng upon it :)

http://sourceforge.net/projects/php-syslog-ng/
or maybe
http://8pussy.org/ (not porn :p syslog web interface)

Maybe this thread could have your interest
http://forum.pfsense.org/index.php/topic,2645.180.html

Keeping logs at embedded systems at least is not possible as we don't write them to disk due to limited writecycles of cf-media. If you really want to have historical data use a remote syslog server. At least in non home environments (and even in those sometimes) there should be a machine around that can capture the systemlogs as this is not a heavy task. I even have a server running at home that has some tasks setup to produce today, yesterday, current week, last week rotating logs.

Geee,

Logging
Syslogd sometimes will go to 100% CPU utilization. Simply click save in the system logging settings tab.

This is already very very known…  :P

[[color=red]edit] and I even managed to eat up 'your time'… You posted just before me  :-[

dnsmasq is the dnsforwarder that you can configure from the webgui. What are you searching for in the filesystem?

Btw, newer snapshots have a states rrd graph. It should log if you reach the limit. Maybe view that graph to see if this really is the case when the problems occur. You even can view it after reboot (if you are not running the embedded version or livecd as you have to do a clean reboot from gui or shell to write the rrds to disk).

@trendchiller:

I created a ticket for that

Thanks, I'll fix it in a bit.

–Bill

You can use a custom port for this, not 22. Also note that we run a script behind the scenes that will block bruteforce attacks against ssh.

Also our head code already has more ssh options to further customize the settings.

To give myself an answer.

The only solution is to configure squid as acceleration proxy and set up a ssl-cert manually. Then squid is able to interrupt ssl connections and handle them by itself. This should ensure logging https connections without having to set anything up withing the client os.

But, unfortunately it seems that the squid package was compiled without the appropriate options.

Cheers,
Manuel

Ha, yeah, it's a busy little machine!! It's been cool being able to test new features shortly after they're added though!!

:D Thanks for all your hard work everyone involved, pfSense rocks!! :D

This is the complete message? There is nothing in front of it telling which service caused the log entry? Also what have been happening before you get that message?

Ok then I won't expect a change till then.  Just wanted to know incase it broke after an update.

Thx - solved

mount -t msdos /dev/fd0 /mnt
cd /mnt
cp config.xml /cf/conf/config.xml
rm /tmp/config.xml
shutdown -r now