<HTML>
<HEAD>
<TITLE>Re: [hobbit] Future of Hobbit</TITLE>
</HEAD>
<BODY>
<FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>Thanks for the info.<BR>
<BR>
I can think of a myriad of reasons why clients aren’t allowed on remote nodes, but in the case that spawned hobcen, it was because the boss said no.<BR>
<BR>
I wrote the hobcen script in early 06 and the p-threaded app came along in mid 06. I was a busy IT Manager back then so it was a get it done and move on kinda thing. I just checked and it is still in production at this time.<BR>
<BR>
After 20 years, I gave up on politics so I could hold onto my technical skills. As it turns out, a 40 hour work week is pretty dang nice. So I thought I would drop the group a note and see what kind of interest there is. Nothing has been submitted as yet.<BR>
<BR>
Cheers,<BR>
<BR>
Tim<BR>
<BR>
On 1/25/08 3:35 PM, "Charles Jones" <jonescr@cisco.com> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>Tim Rotunda wrote:<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'> <BR>
I have not looked at the option you note, however, there are times where<BR>
deploying clients is not an option. I suspect that is why bb-central was<BR>
born and why I developed hobcen. Like I said, it started as a shell script,<BR>
morphed into a C application and then a POSIX-threaded C application. This<BR>
was all based on shared ssh keys, but after coming from a stint in a DC with<BR>
60,000+ nodes on 3 acres of raised floor, I learned very quickly how to use<BR>
ssh pw auth for batch communications that is fast. :-)<BR>
<BR>
We all have issues to resolve and like UNIX, there are 10 different ways to<BR>
solve any one of them.<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'>The pulldata option was added some time ago. You use the keyword in bb-hosts for the hosts you want to pull client data from instead of waiting for a push:<BR>
<BR>
---man page snippet---<BR>
</SPAN></FONT><FONT SIZE="2"><FONT FACE="Monaco, Courier New"><SPAN STYLE='font-size:10.0px'> pulldata[=[IP][:port]]<BR>
This option is recognized by the hobbitfetch(8) utility, and causes it to poll the host<BR>
for client data. The optional IP-address and port-number can be used if the client-side<BR>
msgcache(8) daemon is listening on a non-standard IP-address or port-number.<BR>
</SPAN></FONT></FONT><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'><BR>
As noted it also requires activating the "msgcache" option in the clients clientlaunch.cfg. Basically what happens is the client reports the client-data to "itself", a buffer of sorts, which the Hobbit client then comes along and grabs.<BR>
<BR>
You may find it useful except in the cases you mention where the installation of a client is not possible at all, although I'm not sure why you would be able to run all the commands that the normal client runs, but yet not able to run the normal client?<BR>
<BR>
This is the first I have heard of hobcen...It sounds like it could be useful for some folks until Henrik provides a better solution. Have you submitted it to TheShire?<BR>
<BR>
-Charles<BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Verdana, Helvetica, Arial"><SPAN STYLE='font-size:12.0px'><BR>
</SPAN></FONT>
<pre>This E-mail and any of its attachments may contain Time Warner
Cable proprietary information, which is privileged, confidential,
or subject to copyright belonging to Time Warner Cable. This E-mail
is intended solely for the use of the individual or entity to which
it is addressed. If you are not the intended recipient of this
E-mail, you are hereby notified that any dissemination,
distribution, copying, or action taken in relation to the contents
of and attachments to this E-mail is strictly prohibited and may be
unlawful. If you have received this E-mail in error, please notify
the sender immediately and permanently delete the original and any
copy of this E-mail and any printout.
</pre></BODY>
</HTML>