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 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), though it is listed as a valid share on the serving host.
I can't browse it from a Windows XP system, and a remote SMB mount
from another Linux host fails as soon as I upgrade -- while other shares
continue to work just fine.
Got any other ideas? I'm stumped -- that's why I opened the bug. =)
Christian Perrier wrote:
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 the new samba processes, tried to
connect to the share via a WinXP system, which failed, and then shortly
thereafter shut samba down.
From the logs, it does not fail:
Jun 27 01:04:08 sorrows smbd[4290]: aspiration (192.168.0.11) connect to
service share initially as user shara (uid=1000, gid=104) (pid
+4290)
I actually see nothing that looks like an error in the logs.
What is exactly failing?
I suspect somethign really weird related to the fact that the username
is "shara". Can you just try connecting with another username?
--
# Jesse Molina
# Mail = [EMAIL PROTECTED]
# Page = [EMAIL PROTECTED]
# Cell = 1.602.323.7608
# Web = http://www.opendreams.net/jesse/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
