Comment 46 for bug 407862

I found this page while searching for a fix for the same problem ("rsyslogd was huped..." and no more logging after that (I think cron might have stopped running my scripts then too. can that be?)
anyway, after reading all the technical stuff here, most of which I don't understand (what is a HUP anyway?), I still haven't figured out what 'm supposed to do. Has this bug been fixed, and me getting it is a different bug? is it only fixed in rsyslogd 4.7? will uninstalling rsyslogd and installing sysklogd solve it?