From: Xingdong B. <xin...@er...> - 2009-02-17 11:26:24
|
Hello everyone, I've recently updated yaws from 1.73 to 1.80, it is included in an embedded system with other erlang/otp applications (as in Erlang Web), but i found that the yaws.conf id=myname doesn't work anymore, always got the message when i start the embedded system: =ERROR REPORT==== 17-Feb-2009::10:27:23 === Ignoring 'id = "something"' setting at line 79 So, i cannot start up two or more servers on the same host now, does anyone know the solution to this? Thanks Xingdong |
From: Davide M. <ne...@gm...> - 2009-02-17 12:43:41
|
Hi! Try passing the id on the command line: > erl -yaws debug -run yaws -yaws id server1 -conf priv/yaws.conf > (this works on 1.78) Cheers, Davide On Tue, Feb 17, 2009 at 11:26 AM, Xingdong Bian < xin...@er...> wrote: > Hello everyone, > > I've recently updated yaws from 1.73 to 1.80, it is included in an > embedded system with other erlang/otp applications (as in Erlang Web), > but i found that the yaws.conf id=myname doesn't work anymore, always > got the message when i start the embedded system: > =ERROR REPORT==== 17-Feb-2009::10:27:23 === > Ignoring 'id = "something"' setting at line 79 > So, i cannot start up two or more servers on the same host now, does > anyone know the solution to this? > > Thanks > Xingdong > > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, > CA > -OSBC tackles the biggest issue in open source: Open Sourcing the > Enterprise > -Strategies to boost innovation and cut costs with open source > participation > -Receive a $600 discount off the registration fee with the source code: > SFAD > http://p.sf.net/sfu/XcvMzF8H > _______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list > |
From: Xingdong B. <xin...@er...> - 2009-02-17 14:16:28
|
Thanks, i added -yaws id something to the start_erl, and it worked okay. Just wondering why yaws cannot read id in conf file. Regards Xingdong Davide Marquês wrote: > Hi! > > Try passing the id on the command line: > > erl -yaws debug -run yaws -yaws id server1 -conf priv/yaws.conf > > (this works on 1.78) > > Cheers, > Davide > > On Tue, Feb 17, 2009 at 11:26 AM, Xingdong Bian > <xin...@er... > <mailto:xin...@er...>> wrote: > > Hello everyone, > > I've recently updated yaws from 1.73 to 1.80, it is included in an > embedded system with other erlang/otp applications (as in Erlang Web), > but i found that the yaws.conf id=myname doesn't work anymore, always > got the message when i start the embedded system: > =ERROR REPORT==== 17-Feb-2009::10:27:23 === > Ignoring 'id = "something"' setting at line 79 > So, i cannot start up two or more servers on the same host now, does > anyone know the solution to this? > > Thanks > Xingdong > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San > Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the > Enterprise > -Strategies to boost innovation and cut costs with open source > participation > -Receive a $600 discount off the registration fee with the source > code: SFAD > http://p.sf.net/sfu/XcvMzF8H > _______________________________________________ > Erlyaws-list mailing list > Erl...@li... > <mailto:Erl...@li...> > https://lists.sourceforge.net/lists/listinfo/erlyaws-list > > |
From: Claes W. <kl...@ta...> - 2009-02-17 20:09:40
|
Xingdong Bian wrote: > Hello everyone, > > I've recently updated yaws from 1.73 to 1.80, it is included in an > embedded system with other erlang/otp applications (as in Erlang Web), > but i found that the yaws.conf id=myname doesn't work anymore, always > got the message when i start the embedded system: > =ERROR REPORT==== 17-Feb-2009::10:27:23 === > Ignoring 'id = "something"' setting at line 79 > So, i cannot start up two or more servers on the same host now, does > anyone know the solution to this? I checked this. The --id functionality works just fine. The error report you get is a friendly warning indicating that the "id = something" you have in the yaws.conf file is ignored, because you have already supplied a --id on the command line. So, I added a "id = foo" in my yaws.conf. [klacke@krom]yaws > yaws --daemon [klacke@krom]yaws > yaws --ls Id Status Owner ------------------------------------- kaka stopped klacke foo running klacke So far so good, [klacke@krom]yaws > yaws --id foo --stop stopping yaws with id="foo" [klacke@krom]yaws > yaws --ls Id Status Owner ------------------------------------- kaka stopped klacke Stopped the foo system [klacke@krom]yaws > yaws --id zap --interactive ..... =ERROR REPORT==== 17-Feb-2009::21:08:17 === Ignoring 'id = "foo"' setting at line 7 So, all in all, a major feedback improvement. :-) /klacke |