purple-remote(1) [opensolaris man page]
purple-remote(1) User Commands purple-remote(1) NAME
purple-remote - Send remote commands to Pidgin/Finch SYNOPSIS
purple-remote [-command1] [-command2] [-...] DESCRIPTION
Send remote commands to Purple. This program uses DBus to communicate with Pidgin/Finch. OPTIONS
Each command is of one of the three types: [protocol:]commandname?param1=value1=value2&... FunctionName?param1=value1=value2&... FunctionName(value1,value2,...) The second and third form are provided for completeness but their use is not recommended; use purple-send or purple-send-async instead. The second form uses introspection to find out the parameter names and their types, therefore it is rather slow. Here are some examples: jabber:goim?screenname=testone@localhost=hi jabber:gochat?room=TestRoom=conference.localhost jabber:getinfo?screenname=testone@localhost jabber:addbuddy?screenname=my friend setstatus?status=away=don't disturb quit PurpleAccountsFindConnected?name==prpl-jabber PurpleAccountFindConnected(,prpl-jabber) ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWgnome-cd | +-----------------------------+-----------------------------+ |Interface stability |Volatile | +-----------------------------+-----------------------------+ SEE ALSO
purple-send(1), purple-send-async(1), purple-url-handler(1), attributes(5) purple-remote Manual, http://pidgin.im/ NOTES
Updated by Lei Ju, Sun Microsystems Inc., 2006, 2007. SunOS 5.11 02 Apr 2008 purple-remote(1)
Check Out this Related Man Page
NAGZILLAC(1) General Commands Manual NAGZILLAC(1) NAME
nagzillac - jabber relay bot client SYNOPSIS
nagzillac type^JID^message DESCRIPTION
This manual page documents briefly the nagzillac command. nagzillac is the client for nagzilla that takes the data you hand it as argument and sends it over to the nagzilla daemon that will send the message along. OPTIONS
nagzillac only takes one options that consists of three arguments. They are seperated by the carret character(`^'), although the last argu- ment may contain carrets without any troubles. Here is an explenation of the different parts: type This is the type of the message. It can be either room (which will send the message to a jabber conference room) or chat (target should be a jabber ID). JID This is the target for the message. If you choose room type it has to be a conference room name or complete ID. A single room with- out any @ in it will get sent to the configured conference server. If you choose the chat type the JID has to be the jabber ID of the user to receive the message, either just the user part which will get added the jabber server as domain part, or a full jabber ID. message The final part is the message that will get sent. At the moment it will be put into the body as plain text. Please notice that you will have to quote or escape special characters in the message like white space. FILES
/etc/nagzillac/nagzillac.cfg The configuration file for the nagzilla client. Please see the comments in the file for informations on what to tweak. EXAMPLE
The following sends a chat message to the rhonda user on the default server: nagzillac "chat^rhonda^hi there" This will send a message to a conference room on a different server: nagzillac "room^monitor@jabber.doma.in^alert - do something" SEE ALSO
nagzillad(1). AUTHOR
nagzillac was written by Bill Mathews. This manual page was written by Gerfried Fuchs <rhonda@debian.at> for the Debian project (and may be used by others). 2009-06-03 NAGZILLAC(1)