Usage Examples

Read some real-world examples of our customers and see in which cases Sharity helped to solve their problems.

Unix user needs access to company’s server

If you own the only Unix computer in your company, nobody will be considerate of that fact. The same applies, of course, if you use Linux, FreeBSD or the like: No one would install special software on the server just for you. Not even a configuration option would be changed to help you.

How do you get access to the server in spite of that? Simply install Sharity on your computer. This way the server won’t even notice that you use a different operating system - and you will be able to access all files on the server in the same way as your colleagues.

Developer working on cross platform application

Imagine you are a software developer and your application has to run on Windows and Unix (Solaris, HP-UX, Linux,…). Most of the time you are developing on Windows, but from time to time you have to test on Unix. You could copy the entire source tree over to Unix, do some compile - run - fix cycles and then copy the source tree back. If you have ever tried this, you will know the confusion caused by source tree copies: Which of the two copies is more recent? Confused the direction of the copy again?

You can avoid these problems altogether by installing Sharity on the Unix computer. The source tree can be used directly on the Windows machine - no need to copy it.

Web server runs on Unix, needs files from Windows

Let’s say you have a big dynamic website with a database connection and all sorts of things. This website runs on a Unix server. Now you have to put a catalog online whose images are all on the company’s Windows file server. You can’t just copy all images over to Unix because they are many and updated frequently.

How to solve this problem? You install Sharity on the Unix server. Then you establish a permanent mount by creating a symbolic link pointing into /CIFS and store a login for the web server user in Sharity’s keychain. Now the web server is able to access the files without user interaction.

Backup server collects data from all over the net

You can set up a Unix server for automated nightly backups. It connects to all Windows workstations through Sharity and makes a tar backup of the workstation’s entire disk. The backup script uses Sharity’s command line interface to mount and unmount each workstation. The backup user’s credentials are best stored in the keychain of Sharity.

Specialized software only available for Unix

You have to use a highly specialized software which is only available for Unix? This could for example be a video or image processing software running on an SGI or a workstation controlling hardware. Parts or even most of your workflow is done on Windows, though.

In this case you can use Sharity to couple the file systems: Now an image processing software can render directly to the Windows server where the file may be usable even before it is complete.

You have a similar application? Test the trial version of Sharity.