SourceGear Support

Any command using the secure port must use the -soshome parameter to specify the location of the key. Note that -soshome will get the files to your working folders (as set in the GUI client), so if you don't want that, you must specify -workdir as well.

Sorry, I misinterpreted something you wrote in your first post - I was assuming that you were refreshing the project tree through the GetProjectTree command rather than from the GUI client.

I won't make a bit of difference in terms of speed, though. The CLC does in fact request one file at a time.

Thanks for the update. I still plan on bashing on this for a while, but it's slid down the priority list a bit since you've gotten around the problem. I would suggest adding a delay between the getprojecttree command and the get in your script - a sleep of 60 seconds or so is probably overkill, but ...

It's definitely getting the files - skipped files produce a message something like "File is up to date: (filename)". Is the .sos file updated after the command exits? If not, the CLC isn't able to read the cache, but I can't hazard a guess as to why at this point. I was able to force the c...

I did a quick test on this and it seems to be working, but somewhat confusing. An exclusion doesn't prevent files from appearing in the list, but it does prevent them from being selected when a parent folder is ticked. In your case, if enable the check on the CMN folder, you should see a bunch of fi...

Yeah, we noticed this recently as well, while looking at the issue reported here: http://support.sourcegear.com/viewtopic.php?t=4632. The stream header is being written into the file on disk, which formerly didn't happen. We're guessing that something may have changed in mono, but don't know for sur...

I've managed to reproduce this. It's fine with Vault's integration with Dragnet, so the bug is definitely on the SOS side of things. I've logged a bug, but I can't guess about a workaround or fix until we figure out just what the problem is.

OK, I'm getting somewhere, which leads me to two more questions for you:

1. Are the problem files all at version 1? If not, have they ever been edited on Windows, or only on linux?

2. In addition to Solaris, which linux release are you using? Most of my testing has been of Fedora core 4.

Hmmm... with some more fooling around, I am now seeing some files (but not all) with Native conversion being written with Windows terminators on my Fedora machine. I'm don't really have a clue about what's going wrong, but at least I'm now seeing the same problem. This warrants much deeper digging, ...

Currently there's no way to override the EOL setting in the command line client, but I've logged it and barring something unforseen it will be coming in Vault 3.1.3. I did some testing here on a Fedora core 4 machine with Mono 1.1.8.3 and could not reproduce this problem. I created 4 flat text files...

Xentrax: Could you try to add a comment on our test server (sos.sourceoffsite.com)? It's been able to handle non-Western filenames in the past, but we've never heavily tested it. That machine is a W2K server with version 6.0.306130 of ssapi.dll installed (this is one of the 6.0d versions), with the ...

Forgive me for butting in here, but I spent countless hours with a stopwatch in hand benchmarking SOS and have a certain... investment in this topic! Are the files spread out pretty much evenly in your 42 folders or do a handful of them have a much larger percentage of the files? In my side-by-side ...

Hmm, no wonder I couldn't figure out the resolver stuff. To me verified means that the bug was verified as being found not that QA has verified that the fix was made properly. Perhaps it would be a good idea to list the status codes and give us a brief explanation of each code and how you would rec...

The resolver field is there to assign items for verification after a developer has marked them as completed - essentially it's used to specify a QA person (or a fellow developer) that is assigned to test the bug and decide that it's really really fixed. Resolvers can be assigned particular item cate...

The next thing to do is to explicitly grant the account that operates the service full control over the deploy path (i.e. don't trust the "everyone" settings and manually configure account access). I didn't ask earlier, but is the service operating as a domain account? Is the delpoly path ...