GetLatest doesn't "use checksums..."

lbauer · Post by **lbauer** » Mon Aug 22, 2005 10:46 am

I did following:
1. delete cache files
2. SOS download a project
3. close SOS and delete the local folder
4. use VSS to download the folder

The SOS Client uses a cache file to keep track of the file status. The SOS client compares the file time in the working directory to the time the file was retrieved by the SOS Client.

If the timestamp on the file is later than time in the cache file, the file is considered modified. If the file is checked out and modified, status is Edited. Status is renegade if the file is modified and not checked out.

If you simply place files in a working folder and don't retrieve them with the SOS Client, status can be Unknown.

Doing a get with VSS into the working directory can also cause Unknown or Renegade status.

For best results, use the SOS Client for your file operations, otherwise you'll get unexpected results.

Sky · Post by **Sky** » Wed Sep 14, 2005 3:38 am

1. receive using vss
2. switch to running sos, file stat is unknown
3. use refresh file list button -> all files are blank (great)

1. receive using vss
2. switch to running sos, file stat is unknown
3. use get latest -> all files are downloaded (why?)

1. receive using vss
2. start sos with project tree refresh, file stat is renegade
3. use get latest -> all files are downloaded (not good)

So the option should be named "use checksums when refreshing the file list but not when getting the latest version".

In my opinion sos should not care about file date/time when the checksum option is checked.
VSS also does not care about file date/time if the checksum option is used.

Using only SOS ist not possible because some steps are automated using the VSS Comand line Utility. The SOS Command line Utility does not work (text files are damaged).

I switched back to VSS to get files and use SOS for the other operations (we need SOS becaues running multiple VMWare-OS using one PC crashes VSS if it is startet in several virtual OS whereas SOS works fine).

lbauer · Post by **lbauer** » Wed Sep 14, 2005 8:04 am

If you switch between SOS and VSS like this you will get unexpected results, since SOS was designed to get file status information from a cache file and VSS actions do not update the SOS cache file.

The SOS Command line Utility does not work (text files are damaged).

What version of the SOS Command Line Client are you using? In what way are the files damaged?

Guest · Post by **Guest** » Mon Sep 19, 2005 6:04 am

Hi
I am using SOS 4.1.0, the line breaks are unix-style instead of Windows (cr/lf). Is this bug fixed in 4.1.2?

lbauer · Post by **lbauer** » Mon Sep 19, 2005 8:57 am

In SOS 4.1.2, the Command Line Client no longer gets files with the Unix EOL.

Also, you can now use the -eol parameter on a Get if you want it to be different than the native eol.