See inline responses.
Mary
> -Original Message-
> From: Landon Jurgens [mailto:landon.jurg...@ge.com]
> Sent: Monday, July 27, 2009 1:47 PM
> To: Laser, Mary
> Cc: fossology@fossology.org
> Subject: RE: [FOSSology] Agent terminated prematurely
>
> Mary,
>
> I couldn't understand
Mary,
I couldn't understand how to execute with the -L option. (something
like /etc/init.d/fossology restart -L?)
I looked and found the error log. Here's What I got for the last "event"
since it all occurred within the same minute.
2009-07-27 01:13:02 scheduler[32191] : Child[13]
Hi Landon,
We have recently release fossology 1.1.0 with MANY bug fixes and improvements
to the scheduler. My first recommendation is to upgrade your installation to
this new release and try the analysis again.
If you can't upgrade, here are some other tips for 1.0.0:
Did the error below came
Bob,
Thanks for the suggestions
I believe your 3rd suggestion is what I'm leaning toward --- I have
asked each product team to do a pg_dump to archive the database would
be nice to then 'import/combine' them into a central database
Thanks,
Tom Murray
Senior Systems Engineer
Eas
Team,
I've setup a fossology 1.0.0 with the updated file to allow it to
handle loading directories. I've run two of the 4 jobs successfully but
the last two keep failing. I've had a few jobs fail be resetting them
seems to fix the problem more often than not. These two jobs keep
failing an
On Jul 27, 2009, at 9:31 AM, thomas.j.mur...@kodak.com wrote:
Hello all,
Our company is attempting to scan/analyze all of our product
software. Many locations throughout the world, some product teams
are reluctant to use our central Fossology server so they have setup
their own, So we
Hello all,
Our company is attempting to scan/analyze all of our product software.
Many locations throughout the world, some product teams are reluctant to
use our central Fossology server so they have setup their own, So we
have approximately 7 separate servers collecting OSS info. I'd
7 matches
Mail list logo
