Closed GoogleCodeExporter closed 9 years ago
I need more information, we've never tried to support a bot.
First, what is the actual limnoria command.
Second, how do you get the version data, for example:
limnoria --version or limnoria -v or whatever, show the command and the full
output.
Third: some instances of version output go to stderr, so show this output:
limnoria --version || echo stderr
(assuming the version parameter is --version, of course.
Original comment by inxi-...@techpatterns.com
on 16 Mar 2014 at 6:39
Limnoria is fork of supybot and the commands are supybot-* just like with
gribble and stock supybot.
You get the version information with "version" command at IRC or running
supybot --version which outputs the following (with zsh command included)
% supybot --version
Supybot 0.83.4.1+limnoria 2014.03.11 running on Python3.2.3 (default, Feb 20
2013, 14:44:27)
[GCC 4.7.2]
% supybot --version||echo stderr
Supybot 0.83.4.1+limnoria 2014.03.11 running on Python3.2.3 (default, Feb 20
2013, 14:44:27)
[GCC 4.7.2]
Stock Supybot would output the same, but without +supybot and gribble would say
+gribble, I think.
Original comment by S.Mik...@gmail.com
on 16 Mar 2014 at 7:23
Assuming that the actual method to get the client pid is working, this should
now be supported in 2.1.3.
Confirm if working, with output, and I'll close the issue.
Original comment by inxi-...@techpatterns.com
on 16 Mar 2014 at 11:01
08:08:32 <@Mikaela> +call inxi
08:08:35 <@Supybot> CPU(s)~2 Hexa core Intel Xeon CPU X5675s (-HT-MCP-SMP-)
clocked at 3067.056 Mhz Kernel~3.2.54-grbfs-kapsi x86_64 Up~36 days
Mem~50781.1/145121.9MB HDD~146.8GB(36.6% used) Procs~15 Client~Unknown
python3.2mu client inxi~2.1.3
08:08:37 <@Mikaela> +shell inxi
08:08:38 <@Supybot> CPU(s)~2 Hexa core Intel Xeon CPU X5675s (-HT-MCP-SMP-)
clocked at 3067.056 Mhz Kernel~3.2.54-grbfs-kapsi x86_64 Up~36 days
Mem~50836.0/145121.9MB HDD~146.8GB(36.6% used) Procs~16 Client~Unknown
python3.2mu client inxi~2.1.3
Original comment by S.Mik...@gmail.com
on 17 Mar 2014 at 6:09
No surprise, I didn't expect this to work, I'll give you the same data
collector for this as for the weechat thing.
I would hazard a guess that supybot may be non detectable but you never know.
Original comment by inxi-...@techpatterns.com
on 17 Mar 2014 at 6:28
Just to start, inside of weechat and the bots, run this script, then post the
output.
Also, do this: ps aux > psaux.txt
then upload that ps aux, that must be done while the bot or weechat is running.
There's a trick used to capture konversation new version that may also work for
these bots and weechat.
Original comment by inxi-...@techpatterns.com
on 17 Mar 2014 at 7:57
Attachments:
Put the script somewhere in the system PATH then chmod +x debuggercv then run
it from inside the bot and weechat, that is.
Original comment by inxi-...@techpatterns.com
on 17 Mar 2014 at 7:58
Use this debuggercv instead, it's more likely to work.
Original comment by inxi-...@techpatterns.com
on 17 Mar 2014 at 8:03
Attachments:
08:59:45 <@Mikaela> +call debuggercv
08:59:49 <@Supybot> Starting client version debugger
08:59:49 <@Supybot> ------------------------------------------------------
08:59:51 <@Supybot> EXISTS PPID: 14232
08:59:52 <@Supybot> EXISTS: /proc/14232/exe
08:59:53 <@Supybot> PPID PATH: /usr/bin/python3.2mu
08:59:54 <@Supybot> NAME LOWER: python3.2mu
08:59:55 <@Supybot> CONTAINER PPPID: 1
08:59:56 <@Supybot> Getting pppid client path failed for this reason
08:59:57 <@Supybot> PPPID: 1
08:59:58 <@Supybot> file: -f did not show present: /proc/1/exe
08:59:59 <@Supybot> ------------------------------------------------------
09:00:00 <@Supybot> End client version debugger
09:00:25 <@Mikaela> +shell debuggercv
09:00:26 <@Supybot> Starting client version debugger
09:00:27 <@Supybot> ------------------------------------------------------
09:00:28 <@Supybot> EXISTS PPID: 14516
09:00:29 <@Supybot> EXISTS: /proc/14516/exe
09:00:30 <@Supybot> PPID PATH: /bin/dash
09:00:31 <@Supybot> NAME LOWER: dash
09:00:32 <@Supybot> CONTAINER PPPID: 14232
09:00:33 <@Supybot> PPPID PATH: /usr/bin/python3.2mu
09:00:35 <@Supybot> PPPID PATH LOWER: /usr/bin/python3.2mu
09:00:36 <@Supybot> PPPID CLIENT WORKING NAME: python3.2mu
09:00:36 <@Supybot> ------------------------------------------------------
09:00:38 <@Supybot> End client version debugger
The difference between call and shell is that shell runs the command in shell.
Original comment by S.Mik...@gmail.com
on 18 Mar 2014 at 7:02
Attachments:
Please note: the debugger tool has been added to inxi svn, and is now at:
debuggers/client-version
that version is the one to use from now on.
The issue is resolved, supybot/limnoria/gribble now work using 'shell' call in
IRC client accessing a channel that is run by that bot. The 'call' method does
not work because that just provides a view of the system that is calling
supybot, ie, not the supybot server itself. I think that's how it works anyway.
Anyway, 2.1.10 is tested and works, supybot/limnoria etc version data is
present as desired.
Original comment by inxi-...@techpatterns.com
on 25 Mar 2014 at 11:39
Original issue reported on code.google.com by
S.Mik...@gmail.com
on 15 Mar 2014 at 6:12