public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Angela Marie Thomas <angela@foam.wonderslug.com>
To: Jason Molenda <jason-gcclist@molenda.com>
Cc: overseers@gcc.gnu.org
Subject: Re: waiting for ljrittle's lock in /cvs/gcc/gcc/gcc
Date: Wed, 16 Jul 2003 05:35:00 -0000	[thread overview]
Message-ID: <20030716053917.42378E3A23@foam.wonderslug.com> (raw)
In-Reply-To: Your message of Tue, 15 Jul 2003 22:11:06 PDT. <20030715221106.A77400@molenda.com>


> Folks, I killed off Loren's processes.  I don't think there is any
> useful information to be gathered from the running perl process.

Actually, that turns out not to be true.

There is another log_accum_buzillaified going bonkers.  It's in an
infinite loop.  The bit doing it is from write_sql_batch:

  do
    { 
      $extension++;
      $spoolfile = $SQL_SPOOLDIR . "/tmp." . $extension;
      if ($debug) {
        print STDERR "Spooling SQL -> " . $spoolfile . "\n";
      }
    } while (!sysopen SQL, $spoolfile, O_WRONLY | O_CREAT | O_EXCL, 0644);

SQL_SPOOLDIR is /home/bje/spool which is world writeable, however,
/home/bje is mode 754 (why? I don't know).  This is causing everyone
not in group cygnus and not user bje to fail to create these files.

I don't know why the above is in a loop.  If you can't create the file,
I think you really shouldn't keep trying.  The obvious fix to me is to
do the sysopen and check the return code.  The next obvious thing to do
is make Ben's homedir 755.

Preferences?

--Angela

  parent reply	other threads:[~2003-07-16  5:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-16  4:39 Loren James Rittle
2003-07-16  5:11 ` Jason Molenda
2003-07-16  5:19   ` Loren James Rittle
2003-07-16  5:35   ` Angela Marie Thomas [this message]
2003-07-16  5:38     ` Angela Marie Thomas
2003-07-16  5:47     ` Christopher Faylor
2003-07-16  7:04       ` Angela Marie Thomas
2003-07-16 11:32         ` Ben Elliston

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=20030716053917.42378E3A23@foam.wonderslug.com \
    --to=angela@foam.wonderslug.com \
    --cc=angela@wonderslug.com \
    --cc=jason-gcclist@molenda.com \
    --cc=overseers@gcc.gnu.org \
    /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).