Re: rcs ci and co hang

Re: rcs ci and co hang

[Elfyn McBratney]

> I just tried running strace, and apparently I'm too much of
> a rookie at it, because when I killed it it seemed to leave
> a file under my RCS directory called _0002016, which seems
> to be impossible for me to remove by any means.  That is a
> little worrisome.

Look at the bottom of this...

> Anyway, the test case is trivial.  Let foo.txt be any text
> file.  Just type 'ci foo.txt'.  It hangs immediately.  Here
> is an example of what my screen looks like when it hangs:

I tried your example and I didn't get a hang. I tried it using only a
touched file, a text file with unix line endings and a text file with dos
line endings... :/

Cat you send the output of `cygcheck -svr' as a non-compressed plain-text
attachment to the list please :::::::::::-)

>    03-02-06:15:51:14:/cygdrive/c/TIACore=> ci -mMyMessage foo.txt
>    RCS/foo.txt,v  <--  foo.txt
>
>       <hangs here forever, until I ctrl-C out if it, at which point it
>       says "cleaning up" etc.>
>
> Not that I am using an "RCS" subdirectory for storing my comma-v files
> (or I would *like* to, if any of this worked) but that does not seem
> to matter.  It fails whether I use an RCS subdir or not.
>
> To show you the whole pattern:
>
>    03-02-06:15:49:13:/cygdrive/c/TIACore=> ci Agent.cpp
>    RCS/Agent.cpp,v  <--  Agent.cpp
>
>    RCS: Interrupt                                  <---I killed it here.
>    RCS: Cleaning up.
>    03-02-06:15:51:12:/cygdrive/c/TIACore=>
>
> If you search on the Web you will see many references to this problem.
> A couple that seem to be relevant are:
> http://www.cygwin.com/ml/cygwin/2000-06/msg00018.html (<--See the
follow-up)
> http://www.cvsnt.org/pipermail/cvsnt/2001-December.txt
>
> I hope this helps.  This is a major cygwin showstopper for me.
>
> Thanks very much for your help & interest.
>
> Yours,
>
> Mike
>
> P.S.  Do you have any idea how to get rid of that _0002016 file under
> my RCS directory?
> When I tried to do it from the DOS shell, this is what happened:
>
> C:\TIACore\RCS>dir
>  Volume in drive C has no label.
>  Volume Serial Number is 07D2-060C
>
>  Directory of C:\TIACore\RCS
>
> 02/05/2003  10:27p      <DIR>          .
> 02/05/2003  10:27p      <DIR>          ..
> 02/06/2003  02:11p                   0 _0002016
> 02/06/2003  03:51p                   0 ,foo.txt,
> 02/06/2003  03:51p                   0 _0002164
>                3 File(s)              0 bytes
>                2 Dir(s)  28,407,824,384 bytes free

Hmmm thats odd, I don't get the same results with rcs as you do so that's
expected ;-) Try rebooting and I'm guessing you have admin privs so if after
a reboot you still get  apermissions error just reset the security on the
file(s).


Regards,

Elfyn McBratney
elfyn@exposure.org.uk
www.exposure.org.uk



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: rcs ci and co hang

[Igor Pechtchanski]

Michael,

On Fri, 7 Feb 2003, Michael Drumheller wrote:

> I just tried running strace, and apparently I'm too much of
> a rookie at it, because when I killed it it seemed to leave
> a file under my RCS directory called _0002016, which seems
> to be impossible for me to remove by any means.  That is a
> little worrisome.
>
> Anyway, the test case is trivial.  Let foo.txt be any text
> file.  Just type 'ci foo.txt'.  It hangs immediately.  Here
> is an example of what my screen looks like when it hangs:

Please run the following from a bash prompt:

1) "which ci" and "type -a ci", and paste the output of both in your
   message
2) "cygcheck -svr > cygcheck.txt", and include cygcheck.txt as an
   uncompressed text attachment, as Elfyn recommended
3) "strace -o ci.strace -w ci foo.txt &", wait until ci hangs (you'll see
   its output in a separate window), and look at the end of ci.strace for
   clues.  You may be asked to post it (compressed) later (it might be a
   good idea to paste the output of "wc /tmp/ci.strace", and, maybe,
   "tail -10 ci.strace" before ci is killed, into your message, though).

By the way, it's only worth doing steps 2 and 3 if step 1 shows something
like "/bin/ci" or "/usr/bin/ci" as the first entry in both cases.  If
you get any other result, you're most likely not running the Cygwin RCS,
so this would be off-topic anyway.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
  -- /usr/games/fortune


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: rcs ci and co hang

[Elfyn McBratney]

> I am running into the same problem that Mr. Tolkin encountered
> (ci and co hang on cywin).  His original description is
> http://www.cygwin.com/ml/cygwin/2000-06/msg00018.html.
> I asked him if he ever found a fix (I was unable to find one
> anywhere on the cygwin mailing lists) and he replied
>   "No I gave up on this
>    and subsequently on cygwin."
> Bummer.  Has anything changed on this?
> Thanks,
> MD

Where abouts does rcs c{i,o} hang? You could strace a running/hanging c{i,o}
which may help finding the glitch. Or even better run in under gdb.

Could you provide a test-case on how to make it hang or what process you do
that makes it hang?


Regards,

Elfyn McBratney
elfyn@exposure.org.uk
www.exposure.org.uk



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

rcs ci and co hang

[Drumheller, Michael]

I am running into the same problem that Mr. Tolkin encountered
(ci and co hang on cywin).  His original description is
http://www.cygwin.com/ml/cygwin/2000-06/msg00018.html.
I asked him if he ever found a fix (I was unable to find one
anywhere on the cygwin mailing lists) and he replied
  "No I gave up on this
   and subsequently on cygwin."
Bummer.  Has anything changed on this?
Thanks,
MD

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/