Hmm, it seems that rsyslogd or syslogd-ng would do the job nicely. I guess this could be a good universal solution, as we would need just one config file to configure ALL logging.
So, the minimum implementation could be just to replace syslogd with e.g. rsyslogd and to add the rsyslogd.conf file to the conf editor. A bit more sophisticated would be to define a few user variables and generate the rsyslogd file, like it's been done at the moment with all the other config files. Later on, one could then add some gui options, if necessary. However, for me the simplest solution would already suffice now. How complicated would it be to replace syslogd with rsyslogd in astlinux? Regards Michael Michael wrote: > Or maybe use a more elaborate syslogd implementation instead of busybox, > with a config file describing what level to log from what program to what > file? > > Chris Abnett wrote: > >> Could always log it to a file and have a script that deletes the file >> once a day or such to keep from filling up space in the normal syslog >> file... >> >> -Christopher >> >> -----Original Message----- >> From: James Babiak >> [mailto:[email protected]] Sent: Friday, >> July 23, 2010 11:22 AM To: >> [email protected] Subject: >> Re: [Astlinux-users] Reducing verbosity of hostapd and dnsmasq >> >> It looks like crond is being started with the default verbosity level of >> 8, and 0 is the 'most verbose'. So I doubt there is much that can be >> done for limiting it's output. At least outside of using '-L /dev/null' >> which would eliminate all logging, which probably isn't too desirable. >> >> Sort of the same thing with dnsmasq. While there are options to enable >> even more logging, I don't see anything to reduce what we already get. >> >> -James >> >> On 07/23/2010 10:58 AM, Ionel Chila wrote: >>> Same thing for crond. I have something in crontab running every 5 >>> minutes >> and my >>> syslog is full of contd messages.... Wish there was a way to reduce or >> eliminate >>> those crond messages... Thanks >>> >>> >>> >>> ----- Original Message ---- >>> From: Michael<[email protected]> >>> To: [email protected] >>> Sent: Fri, July 23, 2010 2:57:35 AM >>> Subject: [Astlinux-users] Reducing verbosity of hostapd and dnsmasq >>> >>> Hello >>> >>> I have hostapd and dnsmasq running nicely on my machine (thanks to this >>> mailing list :-) ). However, they are much too verbose to my mind. >>> >>> I haven't found a good way to reduce verbosity so far. For hostapd it >> seems >>> to be hard coded in /etc/init.d/hostapd. If I increase the levels in >>> this file to "3" it seems to be o.k. for me. But I guess, it would be >>> nicer to have a user.conf variable for that, if it is possible. >>> >>> For dnsmasq I haven't found any way so far to reduce logging. So my log >>> is filling up with >>> >>> Jul 23 09:31:47 pbx daemon.info dnsmasq-dhcp[2588]: DHCPREQUEST(br1) >>> 172.17.2.49 00:1f:16:0d:7b:41 >>> Jul 23 09:31:47 pbx daemon.info dnsmasq-dhcp[2588]: DHCPACK(br1) >> 172.17.2.49 >>> 00:1f:16:0d:7b:41 LaptopMB >>> Jul 23 09:31:57 pbx daemon.info dnsmasq-dhcp[2588]: DHCPREQUEST(br1) >>> 172.17.2.49 00:1f:16:0d:7b:41 >>> Jul 23 09:31:57 pbx daemon.info dnsmasq-dhcp[2588]: DHCPACK(br1) >> 172.17.2.49 >>> 00:1f:16:0d:7b:41 >>> Jul 23 09:32:04 pbx daemon.info dnsmasq-dhcp[2588]: DHCPREQUEST(br1) >>> 172.17.2.49 00:1f:16:0d:7b:41 >>> Jul 23 09:32:04 pbx daemon.info dnsmasq-dhcp[2588]: DHCPACK(br1) >> 172.17.2.49 >>> 00:1f:16:0d:7b:41 LaptopMB >>> Jul 23 09:32:14 pbx daemon.info dnsmasq-dhcp[2588]: DHCPREQUEST(br1) >>> 172.17.2.49 00:1f:16:0d:7b:41 >>> Jul 23 09:32:14 pbx daemon.info dnsmasq-dhcp[2588]: DHCPACK(br1) >> 172.17.2.49 >>> 00:1f:16:0d:7b:41 >>> Jul 23 09:32:20 pbx daemon.info dnsmasq-dhcp[2588]: DHCPREQUEST(br1) >>> 172.17.2.49 00:1f:16:0d:7b:41 >>> Jul 23 09:32:20 pbx daemon.info dnsmasq-dhcp[2588]: DHCPACK(br1) >> 172.17.2.49 >>> 00:1f:16:0d:7b:41 LaptopMB >>> Jul 23 09:32:27 pbx daemon.info dnsmasq-dhcp[2588]: DHCPREQUEST(br1) >>> 172.17.2.49 00:1f:16:0d:7b:41 >>> Jul 23 09:32:27 pbx daemon.info dnsmasq-dhcp[2588]: DHCPACK(br1) >> 172.17.2.49 >>> 00:1f:16:0d:7b:41 LaptopMB >>> Jul 23 09:32:34 pbx daemon.info dnsmasq-dhcp[2588]: DHCPREQUEST(br1) >>> 172.17.2.49 00:1f:16:0d:7b:41 >>> Jul 23 09:32:34 pbx daemon.info dnsmasq-dhcp[2588]: DHCPACK(br1) >> 172.17.2.49 >>> 00:1f:16:0d:7b:41 >>> Jul 23 09:32:36 pbx daemon.info dnsmasq-dhcp[2588]: DHCPREQUEST(br1) >>> 172.17.2.49 00:1f:16:0d:7b:41 >>> Jul 23 09:32:36 pbx daemon.info dnsmasq-dhcp[2588]: DHCPACK(br1) >> 172.17.2.49 >>> 00:1f:16:0d:7b:41 LaptopMB >>> Jul 23 09:32:45 pbx daemon.info dnsmasq-dhcp[2588]: DHCPREQUEST(br1) >>> 172.17.2.49 00:1f:16:0d:7b:41 >>> Jul 23 09:32:45 pbx daemon.info dnsmasq-dhcp[2588]: DHCPACK(br1) >> 172.17.2.49 >>> 00:1f:16:0d:7b:41 LaptopMB >>> Jul 23 09:32:54 pbx daemon.info dnsmasq-dhcp[2588]: DHCPREQUEST(br1) >>> 172.17.2.49 00:1f:16:0d:7b:41 >>> Jul 23 09:32:54 pbx daemon.info dnsmasq-dhcp[2588]: DHCPACK(br1) >> 172.17.2.49 >>> 00:1f:16:0d:7b:41 >>> Jul 23 09:33:01 pbx daemon.info dnsmasq-dhcp[2588]: DHCPREQUEST(br1) >>> 172.17.2.49 00:1f:16:0d:7b:41 >>> Jul 23 09:33:01 pbx daemon.info dnsmasq-dhcp[2588]: DHCPACK(br1) >> 172.17.2.49 >>> 00:1f:16:0d:7b:41 LaptopMB >>> Jul 23 09:33:09 pbx daemon.info dnsmasq-dhcp[2588]: DHCPREQUEST(br1) >>> 172.17.2.49 00:1f:16:0d:7b:41 >>> Jul 23 09:33:09 pbx daemon.info dnsmasq-dhcp[2588]: DHCPACK(br1) >> 172.17.2.49 >>> 00:1f:16:0d:7b:41 >>> Jul 23 09:33:10 pbx daemon.info dnsmasq-dhcp[2588]: DHCPREQUEST(br1) >>> 172.17.2.49 00:1f:16:0d:7b:41 >>> Jul 23 09:33:10 pbx daemon.info dnsmasq-dhcp[2588]: DHCPACK(br1) >> 172.17.2.49 >>> 00:1f:16:0d:7b:41 LaptopMB >>> Jul 23 09:33:24 pbx daemon.info dnsmasq-dhcp[2588]: DHCPREQUEST(br1) >>> 172.17.2.49 00:1f:16:0d:7b:41 >>> Jul 23 09:33:24 pbx daemon.info dnsmasq-dhcp[2588]: DHCPACK(br1) >> 172.17.2.49 >>> 00:1f:16:0d:7b:41 LaptopMB >>> Jul 23 09:33:30 pbx daemon.info dnsmasq-dhcp[2588]: DHCPREQUEST(br1) >>> 172.17.2.49 00:1f:16:0d:7b:41 >>> Jul 23 09:33:30 pbx daemon.info dnsmasq-dhcp[2588]: DHCPACK(br1) >> 172.17.2.49 >>> 00:1f:16:0d:7b:41 >>> >>> and so on and so forth. >>> >>> Does anybody know how to limit logging to error messages only? >>> >>> Btw. for the next astlinux version, it might be a good feature to have >>> configurable settings on the gui for logging information, if this is >>> possible. So, in the normal case, one would use just error logging. And >> only >>> if there are problems of some kind, one would switch to debug logging >>> :-) >>> >>> Thanks >>> >>> Michael >>> >>> >>> >> > ---------------------------------------------------------------------------- >> -- >>> This SF.net email is sponsored by Sprint >>> What will you do first with EVO, the first 4G phone? >>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >>> _______________________________________________ >>> Astlinux-users mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/astlinux-users >>> >>> Donations to support AstLinux are graciously accepted via PayPal to >>> [email protected]. >>> >>> >>> >> > ---------------------------------------------------------------------------- >> -- >>> This SF.net email is sponsored by Sprint >>> What will you do first with EVO, the first 4G phone? >>> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >>> _______________________________________________ >>> Astlinux-users mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/astlinux-users >>> >>> Donations to support AstLinux are graciously accepted via PayPal to >> [email protected]. >>> >> >> > ---------------------------------------------------------------------------- >> -- >> This SF.net email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >> _______________________________________________ >> Astlinux-users mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to >> [email protected]. >> >> >> > ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Astlinux-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [email protected].
