From: Zack Weinberg <zack@wolery.cumb.org>
To: overseers@sourceware.cygnus.com
Subject: CVS transient failure
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <20000602185808.E20051@wolery.cumb.org> (raw)
CVS spat out the following:
Cannot open /sourceware/cvs-tmp/#gcc.lastdir.12290,
stopped at /usr/sourceware/bin/commit_prep line 76, <ENTRIES> chunk 2.
cvs server: Pre-commit check failed
Cannot open /sourceware/cvs-tmp/#gcc.lastdir.12290,
stopped at /usr/sourceware/bin/commit_prep line 76, <ENTRIES> chunk 2.
cvs server: Pre-commit check failed
I tried it again and it worked; the disk is not full and the directory
is writable, so I don't know what went wrong. I note there are an
awful lot of stale files in that directory.
It would be nice if that script read
open(FILE, ">$filename") || die("Cannot open $filename: $!\n");
instead of
open(FILE, ">$filename") || die("Cannot open $filename, stopped");
-- then you'd be told the actual error return from open(2) and have a
chance of figuring out what happened.
zw
WARNING: multiple messages have this Message-ID
From: Zack Weinberg <zack@wolery.cumb.org>
To: overseers@sourceware.cygnus.com
Subject: CVS transient failure
Date: Fri, 02 Jun 2000 18:58:00 -0000 [thread overview]
Message-ID: <20000602185808.E20051@wolery.cumb.org> (raw)
Message-ID: <20000602185800.EnrnENUyFdPgKG0n2J7_BlQa3FwWxPtY3WS7RnWzXMM@z> (raw)
CVS spat out the following:
Cannot open /sourceware/cvs-tmp/#gcc.lastdir.12290,
stopped at /usr/sourceware/bin/commit_prep line 76, <ENTRIES> chunk 2.
cvs server: Pre-commit check failed
Cannot open /sourceware/cvs-tmp/#gcc.lastdir.12290,
stopped at /usr/sourceware/bin/commit_prep line 76, <ENTRIES> chunk 2.
cvs server: Pre-commit check failed
I tried it again and it worked; the disk is not full and the directory
is writable, so I don't know what went wrong. I note there are an
awful lot of stale files in that directory.
It would be nice if that script read
open(FILE, ">$filename") || die("Cannot open $filename: $!\n");
instead of
open(FILE, ">$filename") || die("Cannot open $filename, stopped");
-- then you'd be told the actual error return from open(2) and have a
chance of figuring out what happened.
zw
next reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Zack Weinberg [this message]
2000-06-02 18:58 ` Zack Weinberg
2000-12-30 6:08 ` Jason Molenda
2000-06-02 19:08 ` Jason Molenda
2000-12-30 6:08 ` Frank Ch. Eigler
2000-06-02 19:11 ` Frank Ch. Eigler
2000-12-30 6:08 ` Jim Kingdon
2000-06-03 11:39 ` Jim Kingdon
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=20000602185808.E20051@wolery.cumb.org \
--to=zack@wolery.cumb.org \
--cc=overseers@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).