Bug 8599
Summary: | rpc.rstatd forgot to set AF_INET in raw sendmsg. Fix it! | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Tim Waugh <twaugh> |
Component: | rusers | Assignee: | Nalin Dahyabhai <nalin> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-06-06 13:51:12 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tim Waugh
2000-01-19 10:02:45 UTC
The kernel message comes and goes, so it's a bit hard to track this down. The message is more of a problem than what it identifies :-) Perhaps a kernel modification to send SIGSEGV to the current process would help get a core? The problem is the kernel error message rather than the running daemon, as the default fix up works just fine. Adding weird signal behavior to cure a non-existent problem indicated by an anal retentive error message is not the right thing to do. Tim, is this bug still valid or did it get fixed by RH 7? If it has vanished i'd close it with fixed in current release. Read ya, Phil I have no idea. Sorry. I'm changing it to WORKSFORME now as i've not seen the error message on my 7.2 machine anymore... Probably has been fixed with the new glibc anyway (svc_sendreply). Read ya, Phil |