00:03:55 <lockna> ohh, now I get it
00:03:56 <lockna> thanks
00:04:09 <lockna> That makes it perfectly clear for me
00:04:12 <lockna> thank you very much!
00:50:13 <wsky> so i got feedback from some hackers last few days that my FreeBSD server is a fortress >:D
00:58:40 <mangledbits> wsky: Nice!
00:59:05 <wsky> thanks to the dev team brilliance :D
00:59:40 <mangledbits> Anything can be broken, but sane defaults save face xD
02:15:43 <specialbomb> I'm wondering, is it cron's default behavior to email error messages from jobs it runs? I have a bunch of junk in my mail because of it
02:20:46 <mquin> Aye. You can turn it off for the entire crontab by making the MAILTO environment variable empty, or use shell redirection to send the output to a file or /dev/null
02:22:05 <specialbomb> ah, I see. they seem like normal warnings, and the cron job is functioning as its supposed to. just hate all that junk in my mail. will do that
02:26:22 <mquin> A fancier way of dealing with it is provided by a script called 'cronic' - it's in pkg - which collects output but only emits it if the program exits with an error code
02:51:08 <LXGHTNXNG> i should export /etc/periodic, not sure what i want it for, but
02:53:11 <specialbomb> mquin: thats pretty interesting, ill look into that. thanks