I agree -- that does look like my problem.
My initial reaction to reading it is "I'm not using DFS, so I'm not
affected!"
What the release notes seem to be saying though, is that DFS support was
previously enabled by default and now it's being turned off.
Oh well, that's life on unstable.
Quoting Jesse Molina ([EMAIL PROTECTED]):
>
> This bug is squirrelly enough that I'm not terribly interested in following
> it any longer. Let's just close this and forget it ever happened. There
> is a simple workaround anyway. =)
>
> I can still reliably reproduce this error, but with some a
This bug is squirrelly enough that I'm not terribly interested in
following it any longer. Let's just close this and forget it ever
happened. There is a simple workaround anyway. =)
I can still reliably reproduce this error, but with some added
constraints and information, which make my o
> I do realize that there does not appear to be any failures in the log
> files. I turned logging up to 10 and then trolled through it and still
> didn't find anything that I thought was suspicious or unusual.
>
> The failure is that the share can not be accessed in any way
> (apparently), tho
User shara is a legit user account name which has been used long-term.
The share fails in the same way with a completely different non-root
user account as well, so I don't think it's a user-specific issue.
I do realize that there does not appear to be any failures in the log
files. I turne
Quoting Jesse Molina ([EMAIL PROTECTED]):
>
> Attached are logs. Please let me know if I screwed anything up or you
> need more info.
>
> Same problem as before. I upgraded and the "share" share fails. After
> downgrading, everything is fine again.
>
> In the log files, I simply started up
Attached are logs. Please let me know if I screwed anything up or you
need more info.
Same problem as before. I upgraded and the "share" share fails. After
downgrading, everything is fine again.
In the log files, I simply started up the new samba processes, tried to
connect to the share
Quoting Jesse Molina ([EMAIL PROTECTED]):
>
> Hi Christian
>
> I apologize for not responding sooner. I never got your reply due to
> Deb Bug#389475, which caused my mail server to reject messages for a few
> hours. Super.
>
> I'll leave you to be the judge of the bug severity level. I felt
Hi Christian
I apologize for not responding sooner. I never got your reply due to
Deb Bug#389475, which caused my mail server to reject messages for a few
hours. Super.
I'll leave you to be the judge of the bug severity level. I felt it met
the requirements at the time I filed it as repo
severity 429767 normal
thanks
Quoting Jesse Molina ([EMAIL PROTECTED]):
> Package: samba
> Version: 3.0.25a-2
> Severity: important
>
Please don't overflate bug severities.
>
> If a share is named share, as given in the example below, it doesn't work!
> Debugging isn't helpful and testparm
Package: samba
Version: 3.0.25a-2
Severity: important
If a share is named share, as given in the example below, it doesn't work!
Debugging isn't helpful and testparm says it's valid.
Simply renaming the share to anything else, such as myshare, ashare, or
arrggg-whered-my-share-go, are
11 matches
Mail list logo
