Hi,
I have a locked job (access by another user ...) but I do not have the dsadm admionistrator login (nor root)
Is there a way a simple user (like myself) can unlock the job
ds.tools gives me insufficient privilege error
Amos
lock maintenance
Moderators: chulett, rschirm, roy
Without administrative access, the only locks you might have control over are those your userid has. So the answer to your query is most likely "no"
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Premium Member
- Posts: 385
- Joined: Tue Oct 07, 2003 4:55 am
Amos,
I have seen the deadlock daemon stop running after a whle. Are you sure that the process is still active on your box?
If the deadlock daemon is running, the what has probably happened is that your designer client crashed but the UNIX processes associated with that program are still running. If you close all of your DS process and then do a UNIX "ps -ef | grep {YourUserId}" to see if something is still active. If so, do a normal "kill" (not a kill -9) on them. If they won't go away then you could do a kill -9 but the lock won't go away until the deadlock daemon wakes up and checks your system.
There are ways to look at, cleanup and administer your own locks, but I think the method listed above is the best since the deadlock daemon will clean up after you.
I have seen the deadlock daemon stop running after a whle. Are you sure that the process is still active on your box?
If the deadlock daemon is running, the what has probably happened is that your designer client crashed but the UNIX processes associated with that program are still running. If you close all of your DS process and then do a UNIX "ps -ef | grep {YourUserId}" to see if something is still active. If so, do a normal "kill" (not a kill -9) on them. If they won't go away then you could do a kill -9 but the lock won't go away until the deadlock daemon wakes up and checks your system.
There are ways to look at, cleanup and administer your own locks, but I think the method listed above is the best since the deadlock daemon will clean up after you.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Amos,
I was wondering
What were you doing that made the designer crash?
So We all might avoid such actions...
Regards,
I was wondering
What were you doing that made the designer crash?
So We all might avoid such actions...
Regards,
Roy R.
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Time is money but when you don't have money time is all you can afford.
Search before posting:)
Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
-
- Premium Member
- Posts: 385
- Joined: Tue Oct 07, 2003 4:55 am
If you are on version 7.5.x and Designer is crashing specifically while editing a Sequence job, this is a known issue and there is a patch availalbe from Support for this. Other than that, sometimes a reinstall of the Client software helps...
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers