The problem i described happened everytime any change
was made in the wiki and then the wiki was shutdown.
When I tried to start it again (as daemon) it would
not.
I think the snapshot was the problem, since Instiki
wouldn''t save it (unlike when you Ctrl-C running not
as daemon).
Pimki has (in its web edit mode) a way to shutdown.
This would solve it, or else, catch a kill -15 message
and save the snapshot before ending the process.
Andr? Onuki
Message: 4
Date: Sat, 24 Sep 2005 23:13:58 +1000
From: Assaph Mehr <assaph at gmail.com>
Subject: Re: [Instiki] Running Instiki
To: Instiki-users <instiki-users at rubyforge.org>
Message-ID:
<3ff47be905092406131a7424e2 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On 9/24/05, Andr? Onuki <patofuofighter at yahoo.com>
wrote:> I had a problem like that on Linux (waiting
> localhost...) when i run Instiki as a daemon.
>
> Problem was, when i "shutdown" Instiki (by kill -15)
> some files wouldn''t be saved.
>
> So for it to start working again, i''d have to start
> instiki (not in daemon mode), shut it down then
start> in daemon mode again.
Did that ever happen more than once? It seems more
likely a corrupt
snapshot.
> Don''t know exactly if this will work on Windows
(never> tried Instiki for Win).
Instiki runs in daemon via fork, which isn''t available
on Windows, so
it shouldn''t be a problem there.
> You might wanna try Pimki if it doesn''t work for
you.> (hope i don''t get killed by saying such thing)
Nah, this is a polite list ;-)
Besides a facility to gracefully stop the process from
within (instead
of kill) and a few niceties with snapshot management,
I haven''t added
anything that''s vaguely related to this problem to
Pimki, so I doubt
the behaviour in this case would be different.
Cheers,
Assaph
__________________________________
Yahoo! Mail - PC Magazine Editors'' Choice 2005
http://mail.yahoo.com