Search results
Jump to navigation
Jump to search
Page title matches
- [[Category:Policy]]986 bytes (165 words) - 04:38, 11 June 2015
- #REDIRECT [[Privacy policy]]28 bytes (3 words) - 20:31, 8 October 2012
- This policy spells out our procedures and the kind of data protection you can expect fr [[Category:Policy]]3 KB (515 words) - 04:38, 11 June 2015
- 21 bytes (2 words) - 18:45, 18 March 2014
- Our SSH/SSL key policy is as follows. Please make sure all of these are true for all the machines [[Category:Policy]]796 bytes (138 words) - 04:39, 11 June 2015
- Our security policy can be summarized as follows: * [[Sshkey policy]]3 KB (630 words) - 16:28, 30 June 2016
- ...ace policy and applies to those with ssh access to our cluster only. This policy currently applies to [[cluster 2]]. ...erve the following disk usage policy for your account on the cluster. This policy should cover 90% of users, 90% of the time. We understand that research ca6 KB (981 words) - 04:06, 3 June 2015
- #REDIRECT [[Disk space policy]]31 bytes (4 words) - 18:36, 18 March 2014
- * Our policy is the 90/90 rule: to have 90% of compounds updated within the last 90 days Purchasability policy.2 KB (265 words) - 22:20, 2 October 2015
Page text matches
- In [[Zinc12]], our policy was to "flatten" isotopes, removing the labeled atom. One advantage was tha We hope this policy meets with your approval. As always, we welcome [[feedback]].534 bytes (82 words) - 04:37, 11 June 2015
- #REDIRECT [[Privacy policy]]28 bytes (3 words) - 20:31, 8 October 2012
- #REDIRECT [[Disk space policy]]31 bytes (4 words) - 18:05, 18 March 2014
- #REDIRECT [[Disk space policy]]31 bytes (4 words) - 18:36, 18 March 2014
- #REDIRECT [[Disk space policy]]31 bytes (4 words) - 18:36, 18 March 2014
- The reasons for this policy are severalfold: [[Category:Policy]]811 bytes (132 words) - 04:39, 11 June 2015
- Our SSH/SSL key policy is as follows. Please make sure all of these are true for all the machines [[Category:Policy]]796 bytes (138 words) - 04:39, 11 June 2015
- = Policy = At time of writing, this policy is only implemented on [[Cluster 2]].2 KB (282 words) - 04:10, 3 June 2015
- Back to [[Lab Security Policy]]. === Is it lab policy that I can have an ssh key exchange between UCSF and U of T computers? ===2 KB (422 words) - 22:31, 28 December 2018
- cat > ecs-secret-permissions-policy.txt <<EOF ...-role-name ecsInstanceRole --policy-document file://ecs-secret-permissions-policy.txt2 KB (207 words) - 21:42, 20 April 2021
- Enable this policy setting and make sure a checkmark shows up on "Allow BitLocker without a co475 bytes (66 words) - 22:36, 1 June 2018
- (1.2) Read and accept the Compute Canada Acceptable Use Policy. (2.2) for the New Account Application SciNet Usage Policy, read and then click '''Yes'''2 KB (271 words) - 01:22, 31 March 2014
- Add the following policy to the Dynamic Group: create policy4 KB (508 words) - 20:24, 22 March 2023
- ...ace policy and applies to those with ssh access to our cluster only. This policy currently applies to [[cluster 2]]. ...erve the following disk usage policy for your account on the cluster. This policy should cover 90% of users, 90% of the time. We understand that research ca6 KB (981 words) - 04:06, 3 June 2015
- * Our policy is the 90/90 rule: to have 90% of compounds updated within the last 90 days Purchasability policy.2 KB (265 words) - 22:20, 2 October 2015
- * [[Lab Security Policy]] - and security review796 bytes (114 words) - 15:47, 21 April 2014
- Our security policy can be summarized as follows: * [[Sshkey policy]]3 KB (630 words) - 16:28, 30 June 2016
- * [[Lab Security Policy]] * [[Disk space policy]]4 KB (587 words) - 00:43, 8 January 2019
- * Create a policy for your auto scaling dynamic group. This policy needs to be created in the parent compartment to your SlurmAutoScaling comp3 KB (439 words) - 16:39, 9 August 2022
- [[Category:Policy]]986 bytes (165 words) - 04:38, 11 June 2015