> strace -o /tmp/killmenow ftpd -somerandomargs
Wow, I didn't know this, thank you. truss -pf, all the time
on solaris, but I haven't dug that far into linux yet.
> unreachable addresses in resolv.conf
Right, seems like that would almost guarantee a delay. This
was corrected when the nic was added; the person doing the work didn't
step through each part of the change and record results, though. :-/
Daniel Hagerty wrote:
>
> "Toal, Dave" <[EMAIL PROTECTED]> writes:
>
> > All,
> >
> > I'm hoping that someone can shed some light on this
> > problem for me. We have 2 boxes set up on an isolated net
> > through a hub. One is solaris 2.8, the other is red hat
> > gnulinux. wu-ftpd is running on the redhat box. The sun
> > box is listed in its /etc/hosts, and its nsswitch.conf shows
> > hosts: files, only. resolv.conf lists 2 name servers that
> > are not reachable from the isolated net segment.
>
> Your easiest "what's really going on here" is to strace the ftpd
> binary. I've often done things like hack up /etc/inetd.conf to invoke
> daemons as
>
> strace -o /tmp/killmenow ftpd -somerandomargs
>
> in the past. I've found it to be one of the quickest paths to
> enlightenment when you see things fail like this. Often much faster
> than google and certainly less pain than gdb.
>
> That said, having unreachable addresses in resolv.conf is probably
> not something I would do; at least point it at localhost so that
> resolvers get an immediate "ICMP port unreachable" rather than sending
> into a black hole and waiting to time out.
>
> ---
> Send mail for the `bblisa' mailing list to `[EMAIL PROTECTED]'.
> Mail administrative requests to `[EMAIL PROTECTED]'.
---
Send mail for the `bblisa' mailing list to `[EMAIL PROTECTED]'.
Mail administrative requests to `[EMAIL PROTECTED]'.
