[hobbit] Hobbit client for Windows
Indeed. I prefer the Unix command line, so I normally install it anyway. But most will have to install it.
The biggest problem with a Windoze client will be the inconsistency of Windoze. With some versions, a command is standard. With others you require a service pack. Still others require the resource kit. Some versions of Windoze just don't have some commands. It gets quite ugly. I have been informed by my Windoze admin colleague that the behaviour of commands can differ between versions too. Cygwin is consistent, but not complete.
I now understand why Henrik hasn't produced a Windoze client yet.
Cheers Vernon
No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced.
-----Original Message----- From: lars ebeling [mailto:lars.ebeling at leopg9.no-ip.org] Sent: Monday, 28 November 2005 4:36 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Hobbit client for Windows
Hi,
but this means that you have to have Cygwin installed. (?) I have taht but not the resource kit.
Regards Lars
----- Original Message ----- From: "Vernon Everett" <v.everett at afgonline.com.au> To: <hobbit at hswn.dk> Sent: Monday, November 28, 2005 9:22 AM Subject: RE: [hobbit] Hobbit client for Windows
Hi Henrik
Not sure how I forgot this one, but sc will tell you all about services.
Cheers V
No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced.
-----Original Message----- From: Vernon Everett [mailto:v.everett at afgonline.com.au] Sent: Monday, 28 November 2005 4:14 PM To: hobbit at hswn.dk Subject: RE: [hobbit] Hobbit client for Windows
Hi Henrik
Adding the -W to the ps command includes Windoze as well as Cygwin processes. I should have used that in my script. Also, we can monitor swap with the free command. I should have put that in too.
Monitoring services from command line is possible, but only with the resource kit. There is a command called sclist which does it.
As for the client modules - Hmmmm, that's C code. I will leave it to those that know better. :-) The sum total of my C knowledge doesn't extend very far beyond "Hello world".
Cheers Vernon
No trees were killed in the creation of this message. However, many electrons were terribly inconvenienced.
-----Original Message----- From: Henrik Stoerner [mailto:henrik at hswn.dk] Sent: Monday, 28 November 2005 3:21 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Hobbit client for Windows
(Note: I changed the subject)
Hi Vernon,
On Mon, Nov 28, 2005 at 03:01:41PM +0800, Vernon Everett wrote:
Hobbit client runs on Windoze. (Disclaimer applies - see below) :-)
After a little bit of playing around, I managed to compile the client in Windows, and it works.
[snip story of porting the client to Windows with Cygwin]
It's far from perfect but I think it's a good starting point, and there will hopefully be no need for multiple code versions for different platforms.
It's a neat hack, and it does give you the basic functionality. But: There are some severe limitations to this approach. Cygwin's "ps" output for instance only includes the processes that have been started from a Cygwin prompt - not the system processes you'd probably want to check. And monitoring Windows services is not possible, I believe.
Right now it's doing its thing, and sending data back to the server (I think) but the server is not displaying any results other than conn. How can I check what's being received by the server, and what's being done with it?
It probably isn't doing anything with the data. The client data is handled by the hobbitd_client module, which needs to learn how to interpret data from this unknown OS called "windows". If you look at the hobbitd/client/ directory in the Hobbit sources, you'll see there are a bunch of files - one per OS - with code to handle the particular report sent by each OS. Something must be added to deal with the report from your Windows client.
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
_ _
NOTICE: This message and any attachments are confidential and may contain copyright material of Australian Finance Group Limited or a third party. It is intended solely for the purpose of the addressee and any other named recipient. If you are not the intended recipient, any use, distribution, disclosure or copying of this message is strictly prohibited. The confidentiality attached to this message is not waived or lost by reason of the mistaken transmission or delivery to any unintended party. If you have received this message in error, please notify the author immediately or contact Australian Finance Group on +61 8 9420 7888.
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
_ _
NOTICE: This message and any attachments are confidential and may contain copyright material of Australian Finance Group Limited or a third party. It is intended solely for the purpose of the addressee and any other named recipient. If you are not the intended recipient, any use, distribution, disclosure or copying of this message is strictly prohibited. The confidentiality attached to this message is not waived or lost by reason of the mistaken transmission or delivery to any unintended party. If you have received this message in error, please notify the author immediately or contact Australian Finance Group on +61 8 9420 7888.
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
NOTICE: This message and any attachments are confidential and may contain copyright material of Australian Finance Group Limited or a third party. It is intended solely for the purpose of the addressee and any other named recipient. If you are not the intended recipient, any use, distribution, disclosure or copying of this message is strictly prohibited. The confidentiality attached to this message is not waived or lost by reason of the mistaken transmission or delivery to any unintended party. If you have received this message in error, please notify the author immediately or contact Australian Finance Group on +61 8 9420 7888.
Where do I find the resource kit? I unpacked the latest snapshot and started with configure. There where no sudo and fping. What other utilities are needed?
Regards Lars
----- Original Message ----- From: "Vernon Everett" <v.everett at afgonline.com.au> To: <hobbit at hswn.dk> Sent: Monday, November 28, 2005 9:44 AM Subject: RE: [hobbit] Hobbit client for Windows
Indeed. I prefer the Unix command line, so I normally install it anyway. But most will have to install it.
The biggest problem with a Windoze client will be the inconsistency of Windoze. With some versions, a command is standard. With others you require a service pack. Still others require the resource kit. Some versions of Windoze just don't have some commands. It gets quite ugly. I have been informed by my Windoze admin colleague that the behaviour of commands can differ between versions too. Cygwin is consistent, but not complete.
I now understand why Henrik hasn't produced a Windoze client yet.
Cheers Vernon
On Mon, Nov 28, 2005 at 10:09:46AM +0100, lars ebeling wrote:
Where do I find the resource kit? I unpacked the latest snapshot and started with configure. There where no sudo and fping. What other utilities are needed?
I think Vernon did a client-configuration only. Try running Hobbit's configure script with the --client option.
Henrik
On Mon, Nov 28, 2005 at 04:44:30PM +0800, Vernon Everett wrote:
The biggest problem with a Windoze client will be the inconsistency of Windoze. With some versions, a command is standard. With others you require a service pack. Still others require the resource kit. Some versions of Windoze just don't have some commands. It gets quite ugly. I have been informed by my Windoze admin colleague that the behaviour of commands can differ between versions too. Cygwin is consistent, but not complete.
Indeed - despite all the talk about Unix being "fragmented", the Unix API and command-interface is immensely more consistent than the Windows ditto.
I now understand why Henrik hasn't produced a Windoze client yet.
It took me about a week to write all of the Unix clients - Linux, *BSD, AIX, HP-UX, plus the server-side back-end - after which I had a rough implementation that mostly worked, but needed some testing.
It's been about 7 years since I last had the misfortune to do any programming on Windows, so writing a Win32 client would probably take significantly longer than that. The Windows "performance counter" API is just ... abominable.
(If you want to see some live examples of the different ways of thinking in the OpenSource world vs. the Windows world, have a look at this comparison between the Open Document (.odt) XML format and Microsoft's .docx XML format. http://www.groklaw.net/article.php?story=20051125144611543 If you thought using XML would help with interoperability, you're in for a surprise).
My biggest concern for a Windows client is how to support it.
Regards, Henrik
Hi,
I'm absolutely new to this list but I just want to throw my thoughts in.
On the bigbrother extensions-site I saw a perl script implementing the bigbrother protocol. Taking this script as a starting point, using some perl-modules from the Win32::-family, making use of the WMI ( http://msdn.microsoft.com/library/en-us/wmisdk/wmi/wmi_reference.asp ) and a bit of hacking would end up with a hobbit-windows client.
In our IT department (where we use many windows servers, unfortunately), it is not applicable to have cygwin on the servers. So the best way would rather be writing a hobbit client either in perl or C#.
.... Sorry for mentioning C# and discrediting cygwin, but I wanted to state that (IMHO) cygwin is not the (business concerning) answer...
regards, Manuel
----- Message from henrik at hswn.dk --------- Date: Mon, 28 Nov 2005 10:25:48 +0100 From: Henrik Stoerner <henrik at hswn.dk> Reply-To: hobbit at hswn.dk Subject: Re: [hobbit] Hobbit client for Windows To: hobbit at hswn.dk
On Mon, Nov 28, 2005 at 04:44:30PM +0800, Vernon Everett wrote:
The biggest problem with a Windoze client will be the inconsistency of Windoze. With some versions, a command is standard. With others you require a service pack. Still others require the resource kit. Some versions of Windoze just don't have some commands. It gets quite ugly. I have been informed by my Windoze admin colleague that the behaviour of commands can differ between versions too. Cygwin is consistent, but not complete.
Indeed - despite all the talk about Unix being "fragmented", the Unix API and command-interface is immensely more consistent than the Windows ditto.
I now understand why Henrik hasn't produced a Windoze client yet.
It took me about a week to write all of the Unix clients - Linux, *BSD, AIX, HP-UX, plus the server-side back-end - after which I had a rough implementation that mostly worked, but needed some testing.
It's been about 7 years since I last had the misfortune to do any programming on Windows, so writing a Win32 client would probably take significantly longer than that. The Windows "performance counter" API is just ... abominable.
(If you want to see some live examples of the different ways of thinking in the OpenSource world vs. the Windows world, have a look at this comparison between the Open Document (.odt) XML format and Microsoft's .docx XML format. http://www.groklaw.net/article.php?story=20051125144611543 If you thought using XML would help with interoperability, you're in for a surprise).
My biggest concern for a Windows client is how to support it.
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
----- End message from henrik at hswn.dk -----
Hi, I also just signed up for this list. A co-worker suggested to me that there is work being done on a windows client, but I was unable to find a reference to such work in the list archive. We need a windows client at my work. Because we need to customize it, we need the source code, so BB won't do. I am willing to work on such a client, but I want to know what has been done in this area, who else is working on such a project etc. before I invest too much time. Anyone have details on Windows client projects? --PeterD
Manu wrote:
Hi,
I'm absolutely new to this list but I just want to throw my thoughts in.
On the bigbrother extensions-site I saw a perl script implementing the bigbrother protocol. Taking this script as a starting point, using some perl-modules from the Win32::-family, making use of the WMI ( http://msdn.microsoft.com/library/en-us/wmisdk/wmi/wmi_reference.asp ) and a bit of hacking would end up with a hobbit-windows client.
In our IT department (where we use many windows servers, unfortunately), it is not applicable to have cygwin on the servers. So the best way would rather be writing a hobbit client either in perl or C#.
.... Sorry for mentioning C# and discrediting cygwin, but I wanted to state that (IMHO) cygwin is not the (business concerning) answer...
regards, Manuel
----- Message from henrik at hswn.dk --------- Date: Mon, 28 Nov 2005 10:25:48 +0100 From: Henrik Stoerner <henrik at hswn.dk> Reply-To: hobbit at hswn.dk Subject: Re: [hobbit] Hobbit client for Windows To: hobbit at hswn.dk
On Mon, Nov 28, 2005 at 04:44:30PM +0800, Vernon Everett wrote:
The biggest problem with a Windoze client will be the inconsistency of Windoze. With some versions, a command is standard. With others you require a service pack. Still others require the resource kit. Some versions of Windoze just don't have some commands. It gets quite ugly. I have been informed by my Windoze admin colleague that the behaviour of commands can differ between versions too. Cygwin is consistent, but not complete.
Indeed - despite all the talk about Unix being "fragmented", the Unix API and command-interface is immensely more consistent than the Windows ditto.
I now understand why Henrik hasn't produced a Windoze client yet.
It took me about a week to write all of the Unix clients - Linux, *BSD, AIX, HP-UX, plus the server-side back-end - after which I had a rough implementation that mostly worked, but needed some testing.
It's been about 7 years since I last had the misfortune to do any programming on Windows, so writing a Win32 client would probably take significantly longer than that. The Windows "performance counter" API is just ... abominable.
(If you want to see some live examples of the different ways of thinking in the OpenSource world vs. the Windows world, have a look at this comparison between the Open Document (.odt) XML format and Microsoft's .docx XML format. http://www.groklaw.net/article.php?story=20051125144611543 If you thought using XML would help with interoperability, you're in for a surprise).
My biggest concern for a Windows client is how to support it.
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
----- End message from henrik at hswn.dk -----
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
participants (5)
-
henrik＠hswn.dk
-
lars.ebeling＠leopg9.no-ip.org
-
peterd＠ccs.neu.edu
-
v.everett＠afgonline.com.au
-
yoogie＠schurkennetz.de