|
|
|
I'm using a 2.4.xx kernel, where xx is however up-to-date
I happen to be. Some of the things I seemed to be experiencing appeared
to be contradictory to what others had reported, until we sussed out that
2.2 and 2.4 kernels behave differently for certain things. So far, what
I've noticed is:
- File Locking - 2.4 kernels lock files and directories
differently (than 2.2 kernels). This means that Quark Xpress users won't
be able to save files unless you use the option --with-flock-locks .
This will enable correct file locking, but directory locking is still
broken;
- Directory Locking - directories are incorrectly locked,
regardless of byte-range or file locking. Consequently, the network
trash folder can only be accessed by one person (the first person
there). After this, all subsequent accesses by **other people** will
be rejected, as the directory is locked. The user will get a "cannot
store in trash, delete immediately?". If they click ok, the file
will be deleted and **not** stored in the Trash. This doesn't appear
to be the case with normal directories. No error messages will appear
in /var/log/messages to indicate what is occuring.
- New notes - the Network Trash folder works with the
configuration found on the configure page, and a 2.4 kernel. Yay!
Home | Company
Information | Products & Services | Contact
Us
|
|
