02.05.2013 Views

Description - Mks.com

Description - Mks.com

Description - Mks.com

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

When sandbox sharing is removed, users sharing the sandbox each receive an error<br />

message stating the change in sharing configuration the next time they attempt to access<br />

the sandbox or perform an operation on its contents.<br />

--[no]sparse<br />

controls whether or not to make the sandbox sparse.<br />

Making the sandbox sparse with --sparse affects the way the sandbox behaves with the<br />

si ci check in <strong>com</strong>mand and the si co check out <strong>com</strong>mand, as well as si resync .<br />

The intent of a sparse sandbox is that it contains only those working files that are actively<br />

being worked on by you at the time. Using si ci to check in a member to a sparse<br />

sandbox removes the working file from the sandbox (unless you did a check in locked, using<br />

the -l option). Similarly, using si resync on the sandbox will by default remove the<br />

working files for those members which are not locked by you, although you can override this<br />

with si resync --populate in a sparse sandbox, which in effect causes the resync to<br />

behave like it does in a "normal", non-sparse sandbox.<br />

sandbox location...<br />

specifies the path of the sandbox directory including the project file. For example,<br />

C:\sourcecode\framework\scripts\project.pj.<br />

DIAGNOSTICS<br />

See the diagnostics reference page for possible exit status values.<br />

PREFERENCES<br />

Using si setprefs or si viewprefs, you are able to set or view the preference keys for this<br />

<strong>com</strong>mand.<br />

SEE ALSO<br />

Commands:<br />

si createsandbox, si importsandbox<br />

Miscellaneous:<br />

ACL, diagnostics, options, preferences<br />

73 of 457

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!