Sorry I didn't get back to the list earlier. While I didn't isolate the problem, I did eliminate it for now. It was a problem with a windows client. This makes twice that I've seen network printing on windows bork dnsmasq.
Oddly/unfortunately, both the core dump and the ktrace ended up being useless. If you've seen something like this before and have some pointers (other than "don't let windows handle printing") that would prevent something like this from coming up again, please do share your experience with the list. If I were a policeman this would've been me finding the safehouse where the crooks were hiding, but not catching the criminal. I'd love to catch him. -CMP On 5/20/06, Cristobal Palmer <[EMAIL PROTECTED]> wrote:
On 5/20/06, Jason Faulkner <[EMAIL PROTECTED]> wrote: > strace it and post up the output I've been informed that one does not strace on a BSD box. One instead uses 'ktrace' and then examines the output (default == ktrace.out) with 'kdump' for great justice. I'll get back to the list shortly on this one.
-- Cristobal M. Palmer UNC-CH SILS Student TriLUG Vice Chair [EMAIL PROTECTED] [EMAIL PROTECTED] ils.unc.edu/~cmpalmer "Television-free since 2003" < crimsun> the running joke among the Ubuntu archive staff is that we should name the hosts after Aztec deities for great can't-remember-how-to-spell-or-pronounce justice < crimsun> ssh xuihtecuhtli
-- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
