From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: michael <michael@newdream.net>
Cc: nfs@lists.sourceforge.net
Subject: Re: statd segfaults
Date: 18 Feb 2003 10:30:11 +0100 [thread overview]
Message-ID: <shsof5a542k.fsf@charged.uio.no> (raw)
In-Reply-To: <3E51D8C8.8000905@newdream.net>
>>>>> " " == michael <michael@newdream.net> writes:
> ) = 74 sendmsg(4, {msg_name(16)={sin_family=AF_INET,
> sin_port=htons(2670), sin_addr=inet_addr("127.0.0.1")}},
> msg_iov(1)=[{"\336^\313\2\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
> 32}], msg_controllen=24, msg_control=0x8051c20, , msg_flags=0},
> 0) = 32
That looks a bit strange. Why would msg_controllen/msg_control be set
on an RPC call? Are you sure that your statd is linked to the standard
RPC library routines in glibc?
Cheers,
Trond
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-02-18 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 6:55 statd segfaults michael
2003-02-18 9:30 ` Trond Myklebust [this message]
2003-02-19 0:08 ` Neil Brown
2003-04-08 20:01 ` michael
2003-04-09 0:56 ` Neil Brown
2003-04-11 0:57 ` michael
2003-04-08 20:05 ` michael
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=shsof5a542k.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=michael@newdream.net \
--cc=nfs@lists.sourceforge.net \
/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