Error messages and detailed reports about what wconnect is doing go to the debug console. When the debug console is closed wconnect caches the last 100 messages, and its these that are displayed when the debug console is opened. While open the debug console will then continue to record every message that arrives--so you could en up with thousands of messages if you leave it open.
The debug console has its own page in wconnects' properties:
Config var: syslogd
Command line: /a
syslogd(8) is the logging daemon used by most unix servers, and wconnect can act as a client storing messages in it's debug console-- which is handy for monitoring your server. (Windows machines don't use syslogd to do their logging so if you have a windows server this setting is useless and should be turned off.)
Checking this box turns wconnect into a syslog client, but you must then instruct the syslogd to broadcast messages to the machine running wconnect. Edit /etc/syslog.conf file so it contains a line like:
An alternative is to use connectd's thread-attach or machine-attach event scripts to rewrite /etc/syslog.conf on the fly.
This causes wconnect to write a copy of everything it writes to the Debug Console to wconnect.log (or whatever file is named.)
Use this when I ask you to send me a copy of a logfile detailing a bug. This variable isn't saved to the config file and is forgotten between invocations.
The number of messages written to the console is controled by the debuglevel property. At debug level 3 writes every message sent between it and connectd (with the exception of password messages).
Debuglevel's greater than zero would be used only if I ask you to when detailing a bug.