A few things:
1. If you were planning on integrating into the SFW Nevada gate, your
parent workspace should be /ws/sfwnv-gate. You can use "-p
/ws/sfwnv-gate" to override the workspace parent during putback.
2. You need to be logged into the gate machine (sfwnv) to putback
into the gate. (this is on purpose).
3. Your workspace had a leftover lock that appears to be gone now.
(I just looked at it.)
-Norm
Spoorthy H.S wrote:
> Hi,
>
> I am trying to do putback. If I do bringover of some updated file, I
> get the follwoing error.
>
> *Parent workspace: /ws/sfwnv-clone
> Child workspace: /builds1/ss22
> bringover: Cannot obtain a write lock in workspace "/builds1/ss22"
> because it has the following locks:
> User ss224839 has been running a bringover command (pid 8567)
> on mogo for 18 hours, 36 minutes
> (Error 2021)
> *
> If I do "$ps -aef | grep 8567", nothing will be displayed. And I'm
> unable to find that pid even if I do a grep. Can anybody help me how
> to address this asap ?
>
> Thanks
> Spoorthy
> _______________________________________________
> sfwnv-discuss mailing list
> sfwnv-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/sfwnv-discuss
