IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New That would do it
Only entries in there for cron right now are
#cron.*       /var/log/cron.log

and
*.=info;*.=notice;*.=warn;\

auth,authpriv.none;\
cron,daemon.none;\
mail,news.none -/var/log/messages

So I'm not getting much info.

Assuming this can throw a huge amount of crap to disk in a hurry, what do I need to do to make sure I don't eat the disk before I can catch it?
--

Drew
New set it for a single pass first, then debug
once you find the issue, then adjust the schedule.
     Odd cron/links behavior - (drook) - (16)
         I usually use wget for stuff like that. -NT - (malraux) - (12)
             How? - (drook) - (11)
                 cmd >>out.txt file appends output to out.txt - (boxley)
                 Re: How? - (malraux) - (9)
                     Ahh, output-document ... so intuitive - (drook) - (8)
                         typically /var/log/messages and any output is sent to root.. - (folkert) - (7)
                             Nothing in /var/log/messages - (drook) - (6)
                                 Re: Nothing in /var/log/messages - (folkert) - (5)
                                     Nope, not there either - (drook) - (4)
                                         Check /etc/syslog.conf - (scoenye) - (3)
                                             Good point. - (folkert)
                                             That would do it - (drook) - (1)
                                                 set it for a single pass first, then debug - (boxley)
         Figured out the problem ... but not the solution (yet) - (drook) - (2)
             *NOW* I've figured out the problem ... I am a dumbass - (drook) - (1)
                 ICLRPD - (jake123)

Let Us Now Braise Famous Men, those who in their salad days.. imagined that they were of the Caesar variety.
92 ms