That error is safe to ignore, talisman doesn't come with event manager config by default.
de> (I even tried with /talisman/data/gfiles), but upon connection (after ANSI
de> detected) talisman core dumps. If I softlink /talisman/data/gfiles to
de> /talisman/gfiles (the current directory of the talisman process), it seems
de> to work. IE: It doesnt seem to honour the "path" settings?
Hmm, I'll have a look, maybe I have something hard coded by mistake.