Re: Frozen pyds install

Georg Bauer wrote:
> Woops. You could start it with
> 
> pyds-start -f -v
> 
> to see what it does when starting up and how far it comes. This will
> show you more details on what happens within PyDS.
> 
> pyds-start -f -v -e
> 
> will even echo all eventlog messages to stdout. That's especially
> helpfull if you can't access the eventlog any more.

If I start it up with -f -v -e, I get a bunch of normal looking stuff, 
ending:

<archive        > Background process started
events(_log): acquired lock at Wed Mar 17 12:13:54 2004 after 0 seconds
<enclosures     > Background process started
events(_log): acquired lock at Wed Mar 17 12:13:54 2004 after 0 seconds
<timer          > Background process started
<externals      > checking for filesystem changes
Segmentation fault


There's still 14 live threads in the background.  Does this seem like a 
Metakit problem?  I'm expecting it's the one thing that would cause a 
segmentation fault, unless there's other C extensions being used.

   Ian