Bug 48906
Summary: | Samba Client just gets 0xc002002e instead of a text message | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | frank.lammers |
Component: | samba | Assignee: | Trond Eivind Glomsrxd <teg> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | pcfe |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-08-27 01:12:26 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
frank.lammers
2001-07-12 14:17:05 UTC
Normally, I would think it the client programs responsibility to show error messages... why do you think the samba server is capable of doing it for the client? (not rhetorical, I'm interested). I'd also suggest than discussing this on one of the sama-lists, to see what the developers think of it. It is up to the client to make somthing useful out of the error number and there is nothing the Samba server can do in this case. This does not rule out changes in Samba however, as its often possible to return a different error code which will actually be mapped to an error string by the client. In this case I suspect the functionality simply was not implemented in the version of Samba you are using (you failed to mention which one in the report, and I don't know what RH71 shipped with). More recent versions of samba have the 'Take ownership' RPC implemented, but only for root (due to the way unix perms operate). Andrew Bartlett abartlet Red Hat Linux 7.1 shipped with 2.0.7, this was upgraded to 2.0.10 in a security errata. It is up to the client to make somthing useful out of the error number and there is nothing the Samba server can do in this case. This does not rule out changes in Samba however, as its often possible to return a different error code which will actually be mapped to an error string by the client. In this case I suspect the functionality simply was not implemented in the version of Samba you are using (you failed to mention which one in the report, and I don't know what RH71 shipped with). More recent versions of samba have the 'Take ownership' RPC implemented, but only for root (due to the way unix perms operate). Andrew Bartlett abartlet |