Closed
Bug 15609
Opened 25 years ago
Closed 25 years ago
new check-in won't update database
Categories
(Webtools Graveyard :: Bonsai, defect, P3)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: yan.gao, Assigned: terry)
Details
Hi, I am trying to install "Bonsai" as our CVS query system.
(I like it.)
Everything seems Ok except that the new CVS check-in could not
update the database. I followed mozilla/webtools/bonsai/INSTALL
to setup everything. My current status is that whenever a
new check-in happens, an email will be sent to "bonsai-checkin-daemon",
which is already being set as alias as "|/MY_BONSAI_DIR/handleCheckinMail.pl
/MY_BONSAI_DIR".
That "handleCheckinMail.pl" was indeed called. It called another script
"addcheckin.pl". My problem is that the part after line "require 'globals.pl'"
in "addcheckin.pl" won't run at all. I tested it in two ways:
1) If I triggered the "handleCheckinMail.pl" by running
cat what_was_sent_to_bonsai-checkin-daemon
| /MY_BONSAI_DIR/handleCheckinMail.pl /MY_BONSAI_DIR
Everything works well -- the database was updated as expected.
2) But if I tried to trigger the "handleCheckinMail.pl" by email aliase,
as it is designed, I have to comment out that line "require 'globals.pl'",
then the part after that line in "addcheckin.pl" can be run. But I need the
function defined in 'globals.pl'.
I realize this may be a perl question, but anyway I feel you have some perl
experts there. Could you help me with this?
Thanks a lot.
Yan
Build Master
Solect Technology Group
(416)216-6631
Assignee | ||
Comment 1•25 years ago
|
||
Sounds like it could be a permissions problem. Things run as mail will
generally run as a different user than things you run by hand. Check to make
sure that globals.pl is readable by everyone, and that the directories all have
appropriate permissions, and so on.
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Assignee | ||
Comment 2•25 years ago
|
||
In private email, yan.gao@solect.com has confirmed that this was indeed a
problem caused by different settings for different users.
Marking INVALID (because it is a bug in the end-user's setup, not in the code).
Comment 3•25 years ago
|
||
Yep, sounds invalid, whoops I just dropped my salad!
Status: RESOLVED → VERIFIED
QA Contact: matty
Updated•8 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•