2 Sep
2004
2 Sep
'04
10:58 a.m.
There should be something wrong with the cvs checkout. I checked out both
stable and unstable versions yesterday which compiled and run ok. What
stanges me is that if the checkout was incorrect why the built completed
successfully? Did anything change between 30/08/2004 and 31/08/2004? I
dont think so.... Anyway it builds and runs fine now. Concerning the
config file I tryied th e bad checkout with the original (simple) ser
config file.
Thanks for the help,
Markos
On Wed, 1 Sep 2004 19:45:32 +0200, Andrei Pelinescu-Onciul
<pelinescu-onciul(a)fokus.fraunhofer.de> wrote:
On Aug 30, 2004 at 15:39, Markos Vakondios
<mvak(a)intracom.gr> wrote:
[...]
--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/
Hi,
I downloaded the stable cvs versions a couple of days ago but I haven't
been able to make run yet. I have compiled with both bison and yacc as
it
mentioned in a previous post but no luck, even in different PCs.
I am running SuSE 9, SER compiles with warnings about .d files all along
but the build succeeds. Nevertheless, when I try to start it I get the
following output:
The *.d files warning are normal: the first time you compile there are no
dependecies built. Next time you compile you shouldn't get anymore *.d
warnings.
0(2363) DEBUG: register_fifo_cmd: new command
(arg) registered
0(2363) DEBUG: register_fifo_cmd: new command (which) registered
0(2363) DEBUG: register_fifo_cmd: new command (ps) registered
0(2363) DEBUG: register_fifo_cmd: new command (kill) registered
debug=1
0(2363) parse error (1,3-5): parse error
This means parse error on line 1,
columns 3-5.
fk=
log_stderr=
check_via=
dns=
rev_dns=
This is really strange: ser never prints its config file.
[...]
ERROR: bad config file (1 errors)
0(2363) shm_mem_destroy
0(2363) destroying the shared memory lock
Why does it output the config file?And why is it corrupted? Please
help...
How do you start ser? Could you send the config file?
Andrei