Expected '=', but got 'script'

[Aaron Turner]

Grabbed the latest image (201301272037) and built it with most
everything enabled (ssl, curl, lwres, pcre, zlib).

Getting a strange error when i run it:
./build/linux-2.6.32-220.4.2.el6.x86_64-x86_64/tac_plus/tac_plus -d1
-P /root/etc/tac_plus.conf

[snip]
21450: file=/root/etc/tac_plus.conf line=733 sym=[=] buf='='
21450: file=/root/etc/tac_plus.conf line=733 sym=[<string>] buf='STAFF'
21450: file=/root/etc/tac_plus.conf line=733 sym=[{] buf='{'
21450: file=/root/etc/tac_plus.conf line=735 sym=[}] buf='}'
21450: file=/root/etc/tac_plus.conf line=737 sym=[group] buf='group'
21450: file=/root/etc/tac_plus.conf line=737 sym=[=] buf='='
21450: file=/root/etc/tac_plus.conf line=737 sym=[<string>] buf='NETWORK-OPS'
21450: file=/root/etc/tac_plus.conf line=737 sym=[{] buf='{'
21450: file=/root/etc/tac_plus.conf line=739 sym=[}] buf='}'
21450: file=/root/etc/tac_plus.conf line=742 sym=[}] buf='}'
21450: file=/root/etc/tac_plus.conf line=743 sym=[<end-of-file>] buf=''
21451: file=__internal__ line=1 sym=[acl] buf='acl'
21451: file=__internal__ line=1 sym=[script] buf='script'
acl script
__internal__:1: Expected '=', but got 'script'
21451: __internal__:1: Expected '=', but got 'script'


the weird thing is that i don't have the word "script" in my
tac_plus.conf (well I do have some comments with that word in it, but
I even removed those comments and nothing changed).

I tried running the command with the typical >out 2>&1 to capture the
debug output, but all i get is an empty file?

And lastly I'm getting lines like this:

tac_plus[21427] general protection ip:353de3275e sp:9fe04abf0611cacd
error:0 in libc-2.12.so[353de00000+197000]
tac_plus[21433] general protection ip:353de3275e sp:d6777ec623e352e0
error:0 in libc-2.12.so[353de00000+197000]
tac_plus[21444] general protection ip:353de3275e sp:2c66bb8fed03b19
error:0 in libc-2.12.so[353de00000+197000]
tac_plus[21451] general protection ip:353de3275e sp:836d4a030720ef68
error:0 in libc-2.12.so[353de00000+197000]


The only thing I'm wondering is could this be caused because I haven't
run "make install" yet? Didn't want to do that until I've done a
bunch of testing.

Lastly:

$ ./build/linux-2.6.32-220.4.2.el6.x86_64-x86_64/tac_plus/tac_plus -v
tac_plus version 201208240741/PCRE/LWRES

Which is a big WTF since 201208240741 is the current version installed
on this system.

How would I go about testing a new version of tac_plus without first
over writing the currently installed version?


--
Aaron Turner
http://synfin.net/ Twitter: @synfinatic
http://tcpreplay.synfin.net/ - Pcap editing and replay tools for Unix & Windows
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety.
-- Benjamin Franklin
"carpe diem quam minimum credula postero"

[Marc Huber]

Hi Aaron,

On 31.01.13 23:05, Aaron Turner wrote:
> Grabbed the latest image (201301272037) and built it with most
> everything enabled (ssl, curl, lwres, pcre, zlib).
>
> Getting a strange error when i run it:
> ./build/linux-2.6.32-220.4.2.el6.x86_64-x86_64/tac_plus/tac_plus -d1
> -P /root/etc/tac_plus.conf

your binary uses the libraries from the old installation. Please try

./build/linux-2.6.32-220.4.2.el6.x86_64-x86_64/fakeroot/usr/local/sbin/tac_plus -d1 -P /root/etc/tac_plus.conf

instead. Plus, you'll need to add

mavis path =
...build/linux-2.6.32-220.4.2.el6.x86_64-x86_64/fakeroot/usr/local/lib/mavis

(or "mavis path = .../build/%O/fakeroot/usr/local/lib/mavis", but I
didn't test this recently).

I'll look into making the last step obsolete in a future version.

Cheers,

Marc