From: Ed Sweetman <ed.sweetman@wmich.edu>
To: samba@lists.samba.org
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: subdir problems with 2.5.69 and samba 3.x
Date: Mon, 05 May 2003 20:50:59 -0400 [thread overview]
Message-ID: <3EB706F3.8090701@wmich.edu> (raw)
I've tried both the debian devel and cvs pulls of samba and upon
upgrading my kernel to 2.5.69 samba no longer allowed access to
subdirectories of my shares. Windows gives the error "Directory does
not exist" yet all files in the share directory in the directory
supplied by "path" are accessible. This is even true for guest only
services with share security so I'm not sure what's going on here. The
subdirectories are not symlinks and the permissions are world readable
world searchable. Is anyone else having this problem or has this
occurred before so someone can point out what i'm doing wrong. I'm not
subscribed to the list so cc all replies and i can supply any further
info required.
This all worked prior to the kernel upgrade and samba was not changed.
reply other threads:[~2003-05-06 0:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EB706F3.8090701@wmich.edu \
--to=ed.sweetman@wmich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=samba@lists.samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox