>
> I'm playing with yaws in embedded mode to test
> a little application, and i'm facing a strange problem:
>
> In short, it works on one box and doesn't start on another;
> the two machines are basically the same (debian gnu/linux,
> kernels 2.4 and 2.6, erlang and yaws built from sources)
>
> The code is taken from http://yaws.hyber.org/embed.yaws
>
> When i start the gui on the second machin i get back an
> { error, need_restart }
The code in setconf/2 is completely rewritten with the latest
release. It tries to load the new configuration smothly, i.e.
without stopping any virt servers that doesn't have to be stopped.
In earlier relases, all virt servers were stopped and the restarted
with the new config.
There are a number of config options that require restart though, such
as changing the logdir and a bunch of others too.
If setconf/2 returns need_restart, what is needed in embedded mode
is application:stop(yaws), application:start(yaws) and then redo the setconf/2.
If env {embedded, true} is set, yaws will start with an empty conf
What you describe above though, does indeed seem weird. That the same
setconf/2 works on on box and not on the other. It sure as hell isn't
related to the kernel version. Something else is missing here.
I need more data to be able to guide you here ........
/klacke
|