-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 28 April 2002 10:16 am, Jim Hale wrote:
> Now the thing is, if I run webalizer manually, it sits at at a 'DNS > Lookup (5):' prompt until I hit enter and then it seems to process it. > I'm wondering if that's what hung my system last night. Is there a way > to not get it to 'stick'? I haven't seen this here. When there are a lot of addresses to process, I've seen it take as long as 30 seconds at the point you're describing, but it always completes without intervention on my part. I don't normally run webalizer from the command line, though that shouldn't matter. I believe the rpm install sets up a cron job to run it daily. I changed the cron entry to have it run every 4 hours. If you are dealing with a lot of hits on your site, you might try increasing the number of dns children to see if that helps. If you have a lot of addresses that don't resolve in the logs, I suppose it could take some time as the dns children wait for dns replies. Hope that helps, - -- - -Michael pgp key: http://www.tuxfan.homeip.net:8080/gpgkey.txt Red Hat Linux 7.2 in 8M of RAM: http://www.rule-project.org/ - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjzMHNIACgkQn/07WoAb/SusUQCcCbUFZTY2Pj2xN2kAUTiAMQ20 t08AnAvsLbD7kn8BzNz6+NLmj+EYrEWZ =0SXW -----END PGP SIGNATURE----- _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
