On Mon, Mar 2, 2009 at 11:21 AM, r000n <[email protected]> wrote: > > > > On Mar 2, 11:51 am, Renato Botelho <[email protected]> wrote: >> On Fri, Feb 20, 2009 at 9:38 AM, r000n <[email protected]> wrote: >> > 0.8.1.3 >> > New feature: admin can edit Ad-Hoc defaults for users in config.xml >> >http://pyicqt.googlecode.com/files/pyicqt-0.8.1.3.tar.gz >> >> After update FreeBSD ports to 0.8.1.3 I recieve an email from a user >> reporting following problems: >> >> -------------------------------------------------------- >> Hi. >> >> After update i cant discovery transport via ejabberd. >> >> #uname -a >> FreeBSD skuns 7.1-RELEASE FreeBSD 7.1-RELEASE #0 >> >> #pkg_info|grep jabber >> ejabberd-1.1.4_2 Free and Open Source distributed fault-tolerant Jabber >> serv >> jabber-pyicq-transport-0.8.1.3,1 Python ICQ-Transport for Jabber >> >> #sockstat|grep 5347 >> ejabberd python2.5 43897 3 tcp4 127.0.0.1:63875 127.0.0.1:5347 >> ejabberd beam 7970 22 tcp4 127.0.0.1:5347 *:* >> ejabberd beam 7970 25 tcp4 127.0.0.1:5347 127.0.0.1:63875 >> >> #/usr/local/etc/rc.d/jabber-pyicq-transport restart >> Stopping jabber_pyicq. >> Waiting for PIDS: 43897, 43897. >> Starting jabber_pyicq. >> Adding Ad-Hoc defaults for user: xstatus_receiving_mode with value 0 >> Adding Ad-Hoc defaults for user: xstatus_sending_mode with value 0 >> Adding Ad-Hoc defaults for user: xstatus_saving_enabled with value 1 >> Adding Ad-Hoc defaults for user: xstatus_option_smooth with value 1 >> Adding Ad-Hoc defaults for user: xstatus_display_icon_as_PEP with value 1 >> Adding Ad-Hoc defaults for user: xstatus_display_text_as_PEP with value 1 >> Adding Ad-Hoc defaults for user: xstatus_icon_for_transport with value 0 >> Adding Ad-Hoc defaults for user: away_messages_receiving with value 1 >> Adding Ad-Hoc defaults for user: away_messages_sending with value 1 >> Adding Ad-Hoc defaults for user: clist_show_phantombuddies with value 0 >> Adding Ad-Hoc defaults for user: clist_deny_all_auth_requests with value 0 >> Adding Ad-Hoc defaults for user: utf8_messages_sendmode with value 2 >> Adding Ad-Hoc defaults for user: offline_messages_sendenc with value 2 >> Adding Ad-Hoc defaults for user: msgconfirm_sendmode with value 2 >> Adding Ad-Hoc defaults for user: msgconfirm_recvmode with value 1 >> Adding Ad-Hoc defaults for user: user_mood_receiving with value 1 >> Adding Ad-Hoc defaults for user: user_activity_receiving with value 1 >> Adding Ad-Hoc defaults for user: user_mood_receiving with value 1 >> # >> >> On jabber-pyicq-transport-0.8.1.1,1 Python ICQ-Transport for Jabber >> work fine! >> -------------------------------------------------------- >> >> Do you have any idea what could be happening? > Oh, transport parses config file and shows info messages about local > preferences to stdout. > Necessary send them to log > http://groups.google.com/group/py-transports/web/less_noise.diff > Thanks for report!
OK, but what about the guy say "After update i cant discovery transport via ejabberd" ? Do you think this is related with this extra-verbose problem? Thanks -- Renato Botelho --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "py-transports" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/py-transports?hl=en -~----------~----~----~----~------~----~------~--~---
