Please see bug 447820 for a description of this problem. 447820 should be re-opened, but apparently I can't do that.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Given the analysis of the previous bug (bug #447820), this is clearly a BackupPC problem, not a samba issue. IIRC BackupPC needs to have "-N" smbclient option removed from a perl config script. Reassigning to BackupPC so it gets routed to the appropriate maintainer.
(In reply to comment #4) > Given the analysis of the previous bug (bug #447820), this is clearly a > BackupPC problem, not a samba issue. Nope, I absolutely disagree. Nowhere in the SMBCLIENT(1) man page does it say the PASSWD environment variable is ignored when -N is used. Furthermore, this is a change from previous Samba behaviour as shown by the reporter. However, the SMBCLIENT(1) man page does say this about the _password parameter_: "If this parameter is supplied, the -N option (suppress password prompt) is assumed." If we extrapolate that to also include the PASSWD environment variable (which it appears to based on the previous reporters tests), then the easiest way to work around it really is to drop the -N. Unfortunately the man page says almost nothing about the expectations when using PASSWD. If you can do some testing with current versions to see if this behaviour is still present, I will look into removing -N for new installations, regardless of the sad state of the man page.
I no longer have a Windows machine to test current versions on, sorry. This bug is over three years old. The last time I used BackupPC, about three months ago, the commands were still working without the "-N". So, assuming that nothing has changed in the past three months, you won't actually do any harm by removing the "-N". And if the commands continue to fail with the "-N" (as I suspect is the case), then you will be doing quite a bit of good, as it will make BackupPC work properly out of the box. (This bug is especially insidious, as the smbclient man page leads the user to believe that "-N" is necessary.) I agree with you that the smbclient(1) man page is incorrect, in that it does not say that $PASSWD is ignored when "-N" is used. It is also wordy and confusing. I suggest the following: (1) Remove the second sentence in the first paragraph under "password", because it's wrong. ("If this parameter is supplied, the -N option (suppress password prompt) is assumed.") As written, this says that supplying a password turns on "-N", and "-N" causes smbclient to ignore the password on the command line. Fail! (2) As I suggested two years ago, replace the entire text under "-N" in the manpage to say, "Causes smbclient to use no password when accessing the service. Any password in the command line or in the $PASSWD variable will be silently ignored. The user will not be prompted for a password." This wording is clear, concise, and correct; the current wording is both confusing and wrong.
BackupPC-3.2.1-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/BackupPC-3.2.1-1.el6
BackupPC-3.2.1-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/BackupPC-3.2.1-1.el5
BackupPC-3.2.1-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/BackupPC-3.2.1-1.fc15
BackupPC-3.2.1-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/BackupPC-3.2.1-1.fc14
BackupPC-3.2.1-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
BackupPC-3.2.1-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
BackupPC-3.2.1-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
BackupPC-3.2.1-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.