Your message dated Mon, 8 Jan 2024 23:20:22 +0300
with message-id <[email protected]>
and subject line Re: Bug#692551: Symlinks in share root are not shown to client
if share has sticky bit
has caused the Debian Bug report #692551,
regarding Symlinks in share root are not shown to client if share has sticky bit
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
692551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692551
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: samba
Version: 2:3.6.6-3
Severity: normal
Dear maintainer,
I have samba server configured to follow symlinks.
Some of the lines of my smb.conf:
[global]
unix extensions = no
[public]
path = /home/public
wide links = yes
follow symlinks = yes
Generally it works as it should, but If share path has a sticky bit set, client
does not see symlinks placed in the root of this share.
Symlinks placed in subdirs of the share are correctly shown regardless of
sticky bit:
/home/public/symlink1 < not shown on client if /home/public has sticky bit
/home/public/subdir/symlink2 < always shown on client
The moment I do 'chmod -t /home/public', symlinks in share root appear on
client.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (900, 'testing'), (400, 'unstable'), (300, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-686-pae (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8@ISO, LC_CTYPE=ru_RU.UTF-8@ISO (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Version: 2:4.17.0+dfsg-1
On Mon, 14 Nov 2022 16:45:55 +0300 Michael Tokarev <[email protected]> wrote:
Control: tag -1 + moreinfo unreproducible
On Wed, 20 Feb 2019 20:44:47 +0300 Vladimir K <[email protected]> wrote:
> Hi.
> Yes, this is still reproducible with buster's 2:4.9.4+dfsg-2
I can't reproduce this anymore on 4.16. Is it still an issue?
If yes, I need some more accurate instructions to reproduce...
It's been more than a year of inactivity since question is asked, -
I see no reason to keep this bug open. Let's close it now (with
more or less arbitrary version). If you think it is incorrect,
please feel free to re-open this bug report and provide more info
to reproduce the issue.
/mjt
--- End Message ---
