On 26-04-2005 02:10, "Adam R. B. Jack" <[EMAIL PROTECTED]> wrote:
>> Change config.py; configure the logging package by hand (I think that's
>> called "basicConfig()") instead of using a config file, and make it output
>> everything to the screen. We can fix it later, and there's no test to look
>>
On 26-04-2005 06:10, "Adam R. B. Jack" <[EMAIL PROTECTED]> wrote:
>> In fact, I'd much prefer the xml to be:
>> [...]
>> Or rather:
>>
>>
>>
>>
>>
>>
>>
>>
>
> I'd go for this (although perhaps and maybe have more
> attributes on the depend element, to avo
and thus failed.
The problem must have been some apt-get installation that added a
symlink to gij into /usr/bin/java. Obviously Gump still doesn't use
$JAVA_HOME.
I'll remove the symlinks for now.
If you update/upgrade any packages on Brutus, please make sure there
is no /usr/bin/java after tha
Dear Gumpmeisters,
The following 9 notifys should have been sent
*** G U M P
[EMAIL PROTECTED]: Module castor success, but with warnings.
[EMAIL PROTECTED]: Module icu4j failed
[EMAIL PROTECTED]: Module xdoclet success, but with
---
[EMAIL PROTECTED] ~ $ crontab -l | grep java | grep usr
# Watch for /usr/bin/java
3,18,33,48 * * * * /home/gump/check-for-usr-bin-java.sh
[EMAIL PROTECTED] ~ $ cat check-for-usr-bin-java.sh
#!/bin/bash
if [[ -f /usr/bin/java ]]; then
echo "
It seems there's a /usr/bin/java on brutus.apache.or
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Gump Wiki" for change
notification.
The following page has been changed by LeoSimons:
http://wiki.apache.org/gump/VmgumpConfig
The comment on the change is:
some changes still needed
---
It seems there's a /usr/bin/java on brutus.apache.org right now.
That's a problem since gump will use it instead of what it finds
in JAVA_HOME/bin.
Please get rid of it.
Thanks,
- some automated crontab-activated script living in /home/gump
on brutus.
-
On Tue, 26 Apr 2005, Leo Simons <[EMAIL PROTECTED]> wrote:
> That should do it :-D. If this gets messed up again we'll start
> receiving 4 e-mails per hour.
Good idea, thanks.
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
This just popped into my head. Naïve line-based schedule file using simple
commands together with cron could be real nice.
Creating schedules
--
We should have something like
gump schedule-run --profile=public --official
gump schedule-run --profile=public
gump schedule-run -
On Tue, 26 Apr 2005, Leo Simons <[EMAIL PROTECTED]> wrote:
> This just popped into my head. Naïve line-based schedule file using
> simple commands together with cron could be real nice.
+1
Although we may find that we need overlapping Gump runs at times.
Stefan
How about creating a read-only non-executable empty /usr/bin/java file?
The warning test would need to be enhanced of course, but it might
prevent some problems from occurring.
Just a thought.
S.
On 4/26/05, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> On Tue, 26 Apr 2005, Leo Simons <[EMAIL PROT
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Gump Wiki" for change
notification.
The following page has been changed by LeoSimons:
http://wiki.apache.org/gump/VmgumpConfig
The comment on the change is:
mysql instructions
--
On Mon, 25 Apr 2005, Leo Simons <[EMAIL PROTECTED]> wrote:
> In the next version of our in development xml model and in the
> development of gump3, configuration information is left out and
> instead provided on the commandline or using environment
> variables.
+1 to separating environment config
I can't seem to find any sign of live of it on Brutus (the only active
Gump run seems to be the JDK 1.5 one), gump.lock exists and out.txt
ends with
,
| Failed to build project #[(189, 831)] : [asn1-codec], state:Failed
| Build Project: #[(190, 831)] : asn1-der : [state:Unset]
| Perform Upda
> OTOH, debug statements have also worked reasonably for ages. Simplest
thing,
> simplest thing ;)
Yup, I'm there for now, however I was thinking about communication between
two separate developers of plugins, perhaps the latter not being able to
hack debug statements into the former. Still, right
> Could it be that the new "Kill prcess group" stuff is killing too many
> processes, taking the main Gump process down with it?
I don't think it is the new stuff, per-se, but the fact that some old
slipped in with the new. The old killed "the Gump process" 'cos it was
running within a standalone
On Tue, 26 Apr 2005, Adam R. B. Jack <[EMAIL PROTECTED]> wrote:
> I don't think it is the new stuff, per-se, but the fact that some
> old slipped in with the new.
I was just throwing out random ideas ...
> I'll fix it and commit.
Great.
Please note that I haven't removed the lock file yet. I
thanks adam. i was looking into the code myself when i saw ur email :)
will wait for ur patch (both trunk and live...right?)
-- dims
On 4/26/05, Adam R. B. Jack <[EMAIL PROTECTED]> wrote:
>
> > Could it be that the new "Kill prcess group" stuff is killing too many
> > processes, taking the main
> The problem must have been some apt-get installation that added a
> symlink to gij into /usr/bin/java. Obviously Gump still doesn't use
> $JAVA_HOME.
Much as my read of the code would hope to differ, my read of the log say
that Gump (despite efforts) isn't defaulting to $JAVA_HOME/bin/java, bu
> thanks adam. i was looking into the code myself when i saw ur email :)
> will wait for ur patch (both trunk and live...right?)
Nice to have company in there dims. :-)
Let's do a test run, see if things are working (if we can be certain) and
then do a release.
http://wiki.apache.org/gump/G
oops...i already merged your patch to live :(
-- dims
On 4/26/05, Adam R. B. Jack <[EMAIL PROTECTED]> wrote:
> > thanks adam. i was looking into the code myself when i saw ur email :)
> > will wait for ur patch (both trunk and live...right?)
>
> Nice to have company in there dims. :-)
>
> Let'
> oops...i already merged your patch to live :(
I doubt they are harmful, I just wasn't 100% certain they were sure fixes.
regards
Adam
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECT
> I've been wondering whether its a smart idea to change a whole lot of this
> now. I think the Normalizer code and friends shows we can keep the model
the
> same for now yet develop most of our code the way we see fit. The new
model
> will fall out, and we'll immediately know what the transformat
It seems there's a /usr/bin/java on brutus.apache.org right now.
That's a problem since gump will use it instead of what it finds
in JAVA_HOME/bin.
Please get rid of it.
Thanks,
- some automated crontab-activated script living in /home/gump
on brutus.
-
Stefan Bodewig wrote:
On Tue, 26 Apr 2005, Leo Simons <[EMAIL PROTECTED]> wrote:
This just popped into my head. Naïve line-based schedule file using
simple commands together with cron could be real nice.
+1
+1
Although we may find that we need overlapping Gump runs at times.
Stefan
--
Stefan Bodewig wrote:
On Mon, 25 Apr 2005, Leo Simons <[EMAIL PROTECTED]> wrote:
In the next version of our in development xml model and in the
development of gump3, configuration information is left out and
instead provided on the commandline or using environment
variables.
+1 to separating envi
no luck :( kaffe run still dies.
-- dims
On 4/26/05, Adam R. B. Jack <[EMAIL PROTECTED]> wrote:
> > oops...i already merged your patch to live :(
>
> I doubt they are harmful, I just wasn't 100% certain they were sure fixes.
>
> regards
>
> Adam
>
--
Davanum Srinivas - http://webservices.a
This looks 'interesting' :
Kill process group (anything launched by PID 21107)
Kill process group 18226 (anything launched by PID 21107) [from 21109]
for:
pgrpID=os.getpgid(pid)
log.warn('Kill process group %s (anything launched by PID %s) [from
%s]' \
% (pgrpID, pid,
On 26-04-2005 22:24, "Adam R. B. Jack" <[EMAIL PROTECTED]> wrote:
> This looks 'interesting' :
Ooh, then I'd better take a look ;)
> Kill process group (anything launched by PID 21107)
> Kill process group 18226 (anything launched by PID 21107) [from 21109]
>
> for:
>
> pgrpID=os.getpgid(pid)
>
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Gump Wiki" for change
notification.
The following page has been changed by LeoSimons:
http://wiki.apache.org/gump/VmgumpConfig
The comment on the change is:
you need to create tables...
Hey Leo, thanks for taking a peek @ this...
> > Looking at the code, I see no 'setpgid', which is disturbing (to say the
> > least).
>
> Well, there is a setpgrp. That's setpgid(0,0), or something.
Sorry, typo, I meant : os.setpgrp().
> > The logic of this kill means the forked child needs to pl
31 matches
Mail list logo