   
Appendix C: Release Notes
The following has been changed with respect to Beta 0.25:
Bugs fixed:
- Accept more name-types for reverse netbios name lookup. Fixes browsing with old versions of samba.
- Fixed character mapping for netbios names. This fixes browsing of workgroups with non-ASCII characters.
- Fixed bug in the automatic closing of files. Under certain circumstances, Sharity opened an unlimited amount of files.
New Features:
- Basic interoperability with AppleShare 6.2 (and probably other versions).
- Tuned directory cache. Not flushing the entire cache on every directory operation improves performance of file deletion and fixes some possible NFS problems during recursive deletion of large directories.
- Allow better detection of server type. This was necessary because AppleShare IP reports itself exactly like Windows NT.
- Allow browsing of Shares even if no null user can be logged in.
The following has been changed with respect to 2.0:
Bugs fixed:
- If the network connection to the server breaks during running requests, Sharity's transmission system can get into an inconsistent state, letting reconnects fail. Fixed.
- Solaris 7 is not year 2038 safe (interprets NFS timestamps as signed values). Limited the timestamp range to 31 bits for Solaris to work around this problem.
New Features:
- Storing of passwords and mounts can now be disabled.
- If the password database changes, Sharity now parses this file automatically. This is useful if the password database is shared among several machines.
The following has been changed with respect to 2.1:
Bugs fixed:
- Sharity sometimes reported wrong file modification dates with Windows 9x servers. This was a bug in the configuration file, a SMB command which Windows 9x does not support should have been disabled there. Fixed in sharity.cfg.
- If the kernel requests data blocks out of order, Sharity's cache may be confused and deliver the wrong data content. This bug has only been reported with AIX (where it occured in large files) but it may affect other platforms as well. Fixed.
- The "Pseudo-Inode" lookup strategy (which can be configured in the server section of the GUI) did not work on all platforms. Fixed.
- Accessing more than 131072 different files crashed the daemon. Fixed.
The following has been changed with respect to 2.2:
Bugs fixed:
- On several platforms, Sharity's mounts were unaccessible immediately after starting Sharity. This is a bug in the kernel's NFS client implementation, which caches the attributes of the mountpoints too long. Sharity now works around the problem.
- Sharity did crash if an automounted share was unmounted manually. Fixed.
- There was an other bug in the connection state machine: If the connection to a server broke during data transfer, the reconnect could become impossible.
- Made startup script more compatible: check for IRIX and use suitable parameters for renice
- Share-level security servers were not handled well. Changed handling of share password.
- Workaround for kernel-deadlock on Nextstep and Openstep: don't access files within NFS writes.
- Workaround for bug in glibc 2 when used with NIS: don't ask for user-IDs known to be invalid. This can drive glibc 2 into an infinite memory allocation loop eating all your machine's memory resources.
- Newly created files were not closed under all circumstances. Fixed.
- The Sharity daemon could hang when more than 2 different users on one Unix machine accessed the same file simultaneously. Fixed this possible deadlock.
- Browsing of shares with multi-byte characters (Asian character sets) did not work. Fixed capitalization of share names.
New Features:
- Better integration into Openstep's automounting: Setting the sticky-bit on the automounter's symbolic links prevents mounting of all shares once a server is touched.
- The messages logged during server connection and disconnection can now be switched off in sharity.cfg.
- The browse list can be extended by manually configured servers. This is useful for particular off-site hosts which should also appear in the /CIFS directory.
- Browsing can be disabled, leaving only the automounting feature in the /CIFS directory. This may be useful on platforms where the GUI file manager reads directory contents in advance and thus triggers massive mounts or lots of password dialogs.
- Security improvements: Sharity does not require "set-uid-root" programs any more.
- Added a "beta-counter" to the version number.
The following has been changed with respect to 2.3:
Bugs fixed:
- Could not connect to share-level security server without password encryption if share-password was empty. Fixed.
- Fixed an "Internal Error" message if "Cancel" was clicked in GUI's login dialog.
- Under certain circumstances, bad passwords were stored and the user was never asked for the real password again. Fixed.
- Using the -P option to cifslogin with a bad password resulted in an infinite loop. Fixed.
- If the connection to a server failed, the Sharity daemon could run into an infinite loop. Fixed.
- File modification dates could be off by an hour for files created during a different GMT offset than they were viewed. During DST, all files created during non-DST periods were off by one hour and vice versa. Fixed. However, the fix requires that the server and the client switch to/from DST at the same time.
- Fixed possible daemon crash if the server returns an undocumented error code.
- Fixed a bug where the daemon was not started during system boot.
- Fixed an other possible crash which could occur during unmounting of a share.
- Added workaround for NT bug where the end of a directory search is not reported correctly.
- Improved browsing compatibility. Sharity's CIFS folder should work with more network configurations now!
New Features:
- X-Windows GUI displays host name in all windows. This makes it much easier for people running Sharity on a remote host.
- Ignore lookups of certain names in browsing directory. This should fix a lot of unnecessary login dialogs.
- X-Windows GUI starts up in iconic state now.
- New supported platform: Mac OS X
- Sharity makes usable core-dumps now. This should make debugging of daemon crashes much easier.
The following has been changed with respect to 2.4:
Bugs fixed:
- Improved browsing. The CIFS directory should now work on many more network configurations.
- Fixed possible crash during unmounting of CIFS shares.
New Features:
- Login dialog data is preserved if the login fails.
- Mount dialog is pre-initialized from stored mount (if selected).
- Connection domain can now be specified at login panel.
- GUI warns you if a change requires a reboot or reconnect.
- New config option to disable Apple Resource Forks (incompatible with Finder at least up to Mac OS X 10.0.4).
The following has been changed with respect to 2.5:
Bugs fixed:
- Fixed crash when files deeper than 47 levels in directory hierarchy are accessed.
- Fixed possible crash when no browse server is found.
- Allow relative pathes for mount point in 'cifsmount' commandline utility.
- On Mac OS X 10.1: Shares can be unmounted with "Eject" from Finder now.
New Features:
- New configuration option to disable automatic unmount in automounter.
- Automounts can now be stored in the same way as ordinary mounts.
- Server's security mode can now be overridden manually.
The following has been changed with respect to 2.6:
Bugs fixed:
- If files are removed directly on the server, opening a new file in append mode appended at the old file's end, not at offset 0. Fixed.
- Fixed automatic detection of network interfaces for various BSD operating systems.
- Avoid deadlocks with autodiskmount daemon on Mac OS X.
- Finding name of master browse server failed under certain circumstances. Fixed.
- Avoid file system deadlocks on Mac OS X >= 10.1.4.
- Fixed a possible crash in file system operations which create files or directories.
New Features:
- New NFS3 frontend allows files bigger than 4 GB on platforms where NFS3 is sufficiently well supported.
- New config option to return file's create time in Unix ctime.
- Replaced currently useless option to prevent creation of Apple Resource Forks with an option to disable the Trash on Sharity shares. This option is on by default because Finder has a bug with Trashes on Sharity mounted shares. This bug can lead to massive loss of data when you empty the Trash.
   
Sharity Manual for version 2.7 | Copyright (C) 2001 Objective Development | http://www.obdev.at/
|