From: Randolph Chung <randolph@tausq.org>
To: "FAUCHER,DENNIS (HP-USA,ex1)" <dennis_faucher@hp.com>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] nslookup segmentation fault
Date: Tue, 26 Feb 2002 07:39:41 -0800 [thread overview]
Message-ID: <20020226153941.GC7416@tausq.org> (raw)
In-Reply-To: <2F1E6AB90ECAD311943700A0C9E3B154080038E3@xatl03.atl.hp.com>
> Is there a problem with nslookup? Mine returns a segmentation fault. Thank
> you.
paer[8:38] ~% uname -a
Linux paer 2.4.16-64-smp #1 SMP Sat Dec 29 02:33:39 MST 2001 parisc64 unknown
paer[8:38] ~% nslookup -silent www.debian.org
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
Name: www.debian.org
Address: 198.186.203.20
what version of kernel/glibc? did you change anything in
/etc/nsswitch.conf?
the last dozen lines or so of a strace might be useful.
randolph
--
@..@ http://www.TauSq.org/
(----)
( >__< )
^^ ~~ ^^
next prev parent reply other threads:[~2002-02-26 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 15:09 [parisc-linux] nslookup segmentation fault FAUCHER,DENNIS (HP-USA,ex1)
2002-02-26 15:39 ` Randolph Chung [this message]
[not found] <2F1E6AB90ECAD311943700A0C9E3B1540804ED28@xatl03.atl.hp.com>
2002-02-26 19:41 ` Randolph Chung
2002-02-26 21:41 ` Carlos O'Donell Jr.
2002-02-26 22:08 ` Jochen Friedrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020226153941.GC7416@tausq.org \
--to=randolph@tausq.org \
--cc=dennis_faucher@hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox