My server is an AIX box running samba 3.0.4.
I have published a share of symlinked logfiles, because I want to publish
the logs but not the full directories in which the logs live. Here are
some examples:
lrwxrwxrwx 1 hmrbot mis 16 Sep 08 11:43 boxaudit-exempt ->
../../ant/exempt
lrwxrwxrwx 1 hmrbot mis 14 Sep 08 11:41 done.txn ->
../../txn/done
lrwxrwxrwx 1 hmrbot mis 18 Sep 08 11:44 messages.tx2 ->
../../tx2/messages
lrwxrwxrwx 1 hmrbot mis 18 Sep 08 11:44 messages.txn ->
../../txn/messages
lrwxrwxrwx 1 hmrbot mis 17 Sep 08 11:45 spec.qa ->
../../qa/spec.log
These happen to be relative symlinks (../../foo), but absolute symlinks
(/tmp/foo) produce the same behavior I will describe.
I have two linux clients.
- Client A runs samba 2.2.7a and follows the symlinks on the server to see
the files there. All is well.
- Client B runs samba 3.0.7 and tries to follow the symlinks on the
_client_ machine's own filesystem! Needless to say, they don't exist on
the client machine; they're on the server.
Questions:
1) Is this a bug? (Is this bug 2008?
https://bugzilla.samba.org/show_bug.cgi?id=2008 ) Or an intentional
behavior change?
2) Short of downgrading my version of smbclient, can I make Client B behave
like Client A?
