There is one branch and it is locked by other user.
I need to unlock that branch for doing check-in and check-out.
I tried to do it from UI but it is not allowing.
What option do I have to unlock that branch?
I am having the Administrative rights but still getting the error:
Unable to unlock the 'brtype:-----#\-----
No permission to perform operation "unlock"
Must be one of "Object Owner, VOB owner, member of cc group".
Unable to unlock branch type : "-------"
The normal command is cleartool unlock:
cleartool unlock brtype:aBranch#\aVob
That would be using a branch-type-selector (brtype:type-name[#vob-selector]).
You can check if it is locked with a:
cleartool lslock brtype:aBranch#\aVob
However, it does mention (in cleartool lock):
Restriction for locking/unlocking a branch:
Unix: Branch creator, element owner, VOB owner, root
Branch creator, element owner, VOB owner, member of the ClearCase administrators group
If the owner of that branch cannot unlock it, you need to ask to your ClearCase admin.
Related
I'm working on a ClearCase repository. Some of the files in it have, for some reason, execution permissions while they shouldn't (they're text files basically). I'll also mention I'm a user without root privilege.
If I check them out, change their permissions (the usual way, not with ct permission -chmod, which doesn't work), then try to check them back in - I'm told that:
ct: Error: By default, won't create version with data identical to predecessor.
How do I override this default? Or am I going about this the wrong way?
Regarding cleartool checkin, the correct option would be:
-ide/ntical
(meaning cleartool -ide or cleartool -identical: short and long form of the identical option)
Checks in the element even if the predecessor version is identical to the checked-out version.
By default, the checkin operation is canceled in such cases.
But in your case, this should not be needed: you do not need to checkin a protect change.
Try first a cleartool protect command (not cleartool permission)
cleartool protect -chmod 644 aFile
(provided the restrictions allow the command to work, with or without ACLs)
Check also your umask (for instance 002) used in your view (if you are on Unix)
Is there a registry key location in which multiple NON-admin users can read and write ?
I need to write a registry-key as non-admin user in a web-application, that another non-admin user needs to read in his web-applicaton.
So far, in HKLM/SOME_PATH, both users can read, but the one that needs to write cannot write.
And in HKCU/SOME_PATH, one user can write, but the other cannot read it.
Something like
Environment.GetFolderPath(Environment.SpecialFolder.CommonApplicationData);
except with registry instead of files.
Note:
With a windows-system as-is.
Without somebody having to set read/write rights in advance.
HKLM ain't writable for basic-users. Most of subkeys ain't even readable.
HKCU, as its name indicate, is only accessible in the context of the current user.
So :
Is there a registry key location in which multiple NON-admin users can
read and write ?
Registry 'd better be protected !
Without somebody having to set read/write rights...
No
... in advance
Depends. Since the owner basically have all the rights on the key, just make him manage the rights for the users group at the creation of keys (or even, change the owner of the keys since this last one automatically have free_access on it).
However, it can't be done in a basic-user context which seems to be your case ?
I want to give permission for a specific user in my TFS project to do the following.
Create Iterations
Edit the Iterations
Activate the Iteration (In simpler words, 'tick' the Iterations so that they can be seen by others in the team)
MSDN says that
To create or modify areas or iterations, you must either be a member of the Project Administrators group, or your Create and order child nodes, Delete this node, and Edit this node permissions must be set to Allow for the area or iteration node that you want to modify. MSDN
I do not want to give Project Administrator permissions to this specific user.
Hence I gave the following permissions to him in the Parent Iteration.
permissions - screenshot
When logged in as the specific user, TFS says that
You do not have sufficient permissions to configure iterations for this team. You must either be a team administrator or a project administrator.
However, the User can do the following.
Create Child Nodes
Edit the Start/End Dates of existing/new iterations
My question is:
Is there any other way to give a user the permission to 'tick' an iteration without giving him 'Edit collection level permission' or 'project admin permission'
You can create a new TFS group under your team project. Then, grant that group "Edit Project Level Information" permissions. This will allow the user to check the tick box to make the iteration show up in the backlog task board.
What I did was create a "[TEAM PROJECT]\Project Managers" TFS group, I granted that group all permissions on the root node of both the Areas and Iterations. And I also granted that group "Edit Project Level Information." My user was then able to manage areas and iterations - including the "ticking" to activate the iteration.
I have enabled the audit log for Open LDAP for the our system.
However, the log is showing all access details.
For eg; a positive login is having the below entry.
changetype: modify
replace: authTimestamp
authTimestamp: 20150915171011Z
I need to restrict the audit log for only when user account is unlocked or new user account is added or an existing account is deleted.
Tracking every access details will make the log file very big too.
Is it possible to restrict the audit log to track only certain attribute changes?
For eg: a failure attempt has the below entry
changetype: modify
add: pwdFailureTime
pwdFailureTime: 20150915170706Z
I need to track only those attributes which are failed like above.
My slapd.conf file has the below entry.
#
# Audit information
#
overlay auditlog
auditlog /tmp/auditlog.ldif
Thanks,
You can't, as the merest glance at the auditlog documentation shows.
What you may be looking for is the accesslog overlay. It is at least configurable. More probably you should be adding the logging you need into your application.
I am a newbie to perforce and recently started experimenting. I am normal developer with write privileges and was able to delete the entire depot. How can i avoid this while retaining write privileges?
Is there any other way other than Trigger and permission table?
Also, if the developer has deleted a [depot? -msw] and submitted the changelist, how to recover during the following scenarios:
Checkpoint and journal have not been created?
Workspace synced to the depot, and has cleared the workspace eventually.
But the developer is able to view files through the changelist. [??? -msw]
I request someone to clear-up these things for me.
If you give a user write privileges to a directory in Perforce, there is no way to prevent them from deleting it. You can mitigate the damage they can do by narrowing their permissions. Only give them access to what they need, rather than the entire depot.
When you delete files in Perforce, they are not gone, they are just hidden. You can display them with the "Show Deleted Depot Files" option on the filter menu.
They can easily be restored using the "Rollback..." or "Back Out Submitted Changelist N" options.
Files are only truly gone when you use the obliterate command, to which only super users have access.