we compiled samba 2.0.7. on the RTP and it works since we have changed the
tiny tcp/ip stack to the regular one.
today I discovered that samba is able to change the directory flag under
certain conditions. The result is that you cannot
change into the directory or use tar, but I could still browse with the
helpviewer into the directory.
The situation which caused the problem:
I had a symbolic link to " usr/help" and did use the IE 5.0 to browse the
help files and print out some of the pages.
We have to systems installed and I observed the effect on both machines (in
different directories)
does anyone know how to fix it ?
Werner Hettler
does that sound like this: news://8socba$ipk$2@inn.qnx.com
and I thought there was a QSSL reply of a bug in the package manager
wait till patch A?
while talking about SAMBA -
Has anyony investigated patching SAMBA, like for IRIX,
to break oplocks if a local or other network lock is requested
http://www.sgi.com/software/samba/faq.html#NFSandSamba
SGI calls it - kernal oplocks support
Werner Hettler <w.hettler@ideasoft.de> wrote in message
news:8vtpum$sbi$1@inn.qnx.com…
we compiled samba 2.0.7. on the RTP and it works since we have changed the
tiny tcp/ip stack to the regular one.
today I discovered that samba is able to change the directory flag under
certain conditions. The result is that you cannot
change into the directory or use tar, but I could still browse with the
helpviewer into the directory.
The situation which caused the problem:
I had a symbolic link to " usr/help" and did use the IE 5.0 to browse the
help files and print out some of the pages.
We have to systems installed and I observed the effect on both machines
(in
different directories)
does anyone know how to fix it ?
Werner Hettler