Space protection Sample Clauses
The Space Protection clause is designed to safeguard a designated area or premises from unauthorized use, damage, or interference. In practice, this clause may require parties to implement security measures, restrict access to certain individuals, or maintain the area in a specified condition. Its core function is to ensure the integrity and intended use of the space, thereby preventing disputes or losses arising from misuse or neglect.
Space protection. CASTOR already implements a sophisticated protection mechanism which meets the requirements outlined in this document. The 'black and white' lists provide both negative and positive access rights to spaces. However, it is based on uid/gid rather than DN or FQAN. In the next three months an administrative interface will be made available for CASTOR administrators to easily set white and black lists.
Space protection. Spaces in StoRM will be protected via ACLs. ACLs are based at the moment on user DN and FQANs. Wildcards on DN or FQAN are also supported. ACLs apply at the moment to space token descriptions only (and not to space tokens). However, in StoRM there is a one-to-one mapping between space tokens and space token descriptions. Therefore, setting ACLs on space token descriptions is equivalent to setting ACLs on space tokens. This is an advantage for site administrators that do not have to deal with the internal representation of the space tokens. It is in the short term plans to make the ACLs compliant with the ones defined in this document. Service administrators can manage space protection via StoRM configuration files.
Space protection. Spaces in DPM belong to a group (or possibly a user, but usually a group) and to be able to write into a space a user has to belong to the space's group. In that respect the space is protected. The requirement's example of generic users triggering staging is not a concern for DPM for the WLCG.
Space protection. Spaces in DPM belong to a group (or possibly a user, but usually a group) and to be able to write into a space a user has to belong to the space's group. In that respect the space is protected. The requirement's example of generic users triggering staging is not a concern for DPM for the WLCG. Sites would like to be able to have a list of FQANs which are allowed to write to a space and not just one FQAN which is currently allowed. It is expected a change to allow for the list can be made within three months. However the timeframe is still subject to agreement and this will be moved to section 6 in a later revision of this document. Section 6 will also list time estimates on the other proposed features for the long term changes.
Space protection. Spaces in StoRM will be protected via ACLs. ACLs are based at the moment on user DN and FQANs. Wildcards on DN or FQAN are also supported. ACLs apply at the moment to space token descriptions only (and not to space tokens). It is in the short term plans to make the ACLs compliant with the ones defined in this document. Service administrators can manage space protection via StoRM configuration files.
Space protection. If additional space protection is required, it will be the responsibility of the owner/owner’s representative to take the necessary precautions. ▇▇▇▇▇▇ assumes no responsibility or liability for damages as a result of the failure of the owner to adequately protect the space. Arista is further not obligated to honor any warranties associated with the equipment or be liable for any property damage if you have failed to maintain the equipment free of debris, free of water damage, such as spillage into the system, unexpected exposure to water, or any similar situation, overcrowding and all other conditions which would result in damage to the equipment.