From: "Tolkin, Steve" <Steve.Tolkin@fmr.com>
To: cygwin@sourceware.cygnus.com
Subject: rcs ci fails under cygwin; ci foo hangs leaving a lock file RCS/fo_
Date: Thu, 01 Jun 2000 08:21:00 -0000 [thread overview]
Message-ID: <F614BF868E0DD411A5A700508B957E0038D007@MSGBOS679NTS.fmr.com> (raw)
I have a binary of the 5.7 version of RCS files
> ls -l ci
-rwxr-xr-x 1 administ Administ 14848 Mar 28 1999 ci*
I have been using this successfully in a DOS box for months.
But when I run it under cygwin ci foo hangs (for every file foo I have
tried).
It creates a lock file named RCS/fo_
but never gets any further. What is the problem?
rcsdiff and co work fine in cygwin, so I suspect the problem is that some
file is not writable.
Here is a tiny test case:
540/temp> ci foo
RCS/foo <-- foo
-- I must manually break
out here
541/temp> ls -l RCS
total 16
drwxrwxrwx 2 administ Administ 0 Jun 1 11:17 ./
drwxrwxrwx 6 administ Administ 32768 Jun 1 11:17 ../
-r--r--r-- 1 administ Administ 0 Jun 1 11:17 fo_
When I am in emacs a checkin works correctly,
but I am not sure that ci program is being run, or if emacs is doing this
itself.
I must rm -f RCS/fo_ before I can check in the file from DOS or emacs, so I
assume that
it is the lock file.
I am not sure how to learn what version of cygwin I am running.
I downloaded it via setup.exe 2 days ago.
> bash --version
GNU bash, version 2.04.0(10)-release (i586-pc-cygwin32)
Copyright 1999 Free Software Foundation, Inc.
Thanks,
Steve
--
Steven Tolkin steve.tolkin@fmr.com 617-563-0516
Fidelity Investments 82 Devonshire St. R24D Boston MA 02109
There is nothing so practical as a good theory. Comments are by me,
not Fidelity Investments, its subsidiaries or affiliates.
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-06-01 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-01 8:21 Tolkin, Steve [this message]
2000-06-01 11:00 ` Uwe H. Steinfeld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F614BF868E0DD411A5A700508B957E0038D007@MSGBOS679NTS.fmr.com \
--to=steve.tolkin@fmr.com \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).