Windows is not a professional and serious Operative System :P Sorry!
Best regards 2010/6/17 Michael Weinbergs <[email protected]> > Thanks for all the comments and suggestions.. just an update that I > managed to build with CYGWIN without too many problems (surprise!) > > If anyone wants to know how to build under cygwin in the future: > 1. Install CYGWIN > 2. Install modules: gcc, openssl-devel, make, gcd, pcre (I think that > was all ;) > 3. Decompress the pound-2.5.tgz tar/gz > 4. build the platform > (I wanted to have the files in c:\pound\bin and c:\pound\etc thus I used > the "--prefixc:/pound" - note the slash direction CYGWIN needs the c: > to understand what you are trying to do!) > ./configure --prefixc:/pound --with-ssl --disable-super > make > > 5. make the directory structure under windows > mkdir /cygdrive/c/pound > mkdir /cygdrive/c/pound/bin > mkdir /cygdrive/c/pound/etc > > 6. copy the cygwin running environment > cp pound*.exe /cygdrive/c/pound/bin > cp /usr/bin/cygcrypto*.dll /cygdrive/c/pound/bin > cp /usr/bin/cygwin1*.dll /cygdrive/c/pound/bin > cp /usr/bin/cyggcc*.dll /cygdrive/c/pound/bin > cp /usr/bin/cygpcre*.dll /cygdrive/c/pound/bin > cp /usr/bin/cygssl*.dll /cygdrive/c/pound/bin > > Go back to windows, cd into c:\pound\bin and do a "pound.exe -v" > (remember - any posix folder structures in your pound.cfg (ie. You .pem > file location) will need changing.) > > I am testing this as a non-daemon and appears to work fine right now... > very little impact to CPU etc.. certainly looks promising! > Hope this helps someone else in the future. > Mike > -----Original Message----- > From: Michael Weinbergs > Sent: Thursday, 17 June 2010 9:23 AM > To: [email protected] > Subject: RE: [Pound Mailing List] RE: Ported to Windows? > > I should have been a little clearer in my post :) > > 1) Distribute bad choice of words... pound will be behind three remote > links as "backups". Their configs will be identical. Distribution is the > word I chose for getting replicative setups (pound.cfg) on each remote > link. I didn't mean "distributed-as-in-clustering". Sorry. > > 2) I run vSphere in production and DR now - and there is a separate > project to P2V the remote sites to vSphere... but unfortunately this > pound-project has been bumped up the list - chicken-or-egg scenario. The > Windows-based solution I seek is only temporary, until I get those sites > virtualised. (BTW: I did consider VMware server/workstation at the sites > - but they are just too underpowered - the virtualises project is part > of a hardware refresh). > > 3) after I sent the post I started to think about CYGWIN. That's my > project for today. > I eventually noticed (once I discredited all of spurious google results) > that this is well-trodden ground (eventually found someone posted a > W32-Pound-2.3-no-ssl on the 'net).. I'll see how I go with this today > and it might be the perfect temporary solution (yes, I do understand it > will be slow and sluggish... but better than what I have now!) > > Just so you understand where I come from here: we had a 6 hour outage > recently that even a BGP re-route could fix (the outage was in the ISP's > core and took out all the BGP routes - as you can imagine - a big > problem affecting a LOT of companies and a 1 in a million...). it was an > outage that was "never suppose to ever happen" - but it did. > Of course, this all came about whilst I was concurrently doing an > ISO270002 audit... so is now in the register and thus - "urgent" ;) > That's where I came across pound. With it I can keep provision of > webservices via a few other (different ISP) links.. and mitigate the > risks. > > Thanks to you all for your comments.. my apologies for not being clearer > in my post. > > While I'm here: > Does anyone know a trick to get DNS "IN A" records to have a preference > (like "IN MX Preference ")? > My next hurdle is - now I have pound at each of the sites - I only want > the remote sites involved during an outage. > If I put the IP's in to the A record (or CNAME them) - I will > essentially be doing round-robin or "first reply".. > The only way I can think to do this is to manually manipulate the NS > records, wait for DNS cache to refresh to pick up the new sites. > I'm concerned that the backup links will be slow so I don't want any > client to use them unless the core link is down. > If anyone has an idea to that I would appreciate feedback! > > > > > __________________________ > Michael Weinbergs > Network Administrator > -----Original Message----- > From: Joe Gooch [mailto:[email protected]] > Sent: Thursday, 17 June 2010 12:04 AM > To: [email protected] > Subject: [Pound Mailing List] RE: Ported to Windows? > > You say distribute... which in my experience is fraught with problems :) > > Pound depends on libpthread, which is of *nix design. The only way I've > been able to get it to run on Windows is using Cygwin. MSys didn't > compile right, and I don't have the requisite knowledge to do a MSVC++ > native binary, replacing pthread with appropriate Win APIs. So cygwin > is really the only option. > > I've compiled binaries for pound on Cygwin before... They generally > don't perform as well as the Linux native ones I use, which isn't > surprising given the emulation layer. Plus, if you have more than one > different version of cygwin.dll on the same machine you can have all > sorts of stability issues. (for instance, openssh and pound with > different dlls) > > The best option is to install cygwin on the server and compile it there. > Make sure you install the compiling tools (make, gcc, etc) and the > libraries you need (pcre, openssl, etc), and cygrunsrv if you want to > run it as a service. Last time I compiled with ./configure > --disable-super --with-ssl. > > From that point on you can configure and use it normally... You can use > cygrunsrv to install it as a service. > > Compiling on one machine and trying to distribute is more problematic > because of cygwin.dll collisions... I've done it before, just copy > pound.exe to a directory on the destination server. Run it and copy > every dll it complains about from the source system to the destination > folder. Repeat until all dlls are copied. Make sure no other > cygwin.dll or cygwin1.dll is on the system. > > I wish you luck! > > Joe > > > > -----Original Message----- > > From: Michael Weinbergs [mailto:[email protected]] > > Sent: Wednesday, June 16, 2010 2:54 AM > > To: [email protected] > > Subject: [Pound Mailing List] Ported to Windows? > > > > I have a need to distribute a simple pound setup on a win32 machine > > (XP) > > to solve an immediate need. > > > > Does anyone know if pound has been compiled and where I might find it > > if > > it has (prefer vs. 2.5 if possible) > > > > Michael > > > > > > > ####################################################################### > > ############## > > This e-mail message has been scanned for Viruses and Content and > > cleared > > by NetIQ MailMarshal > > > ####################################################################### > > ############## > > > > > ####################################################################### > > ############## > > The information contained in this email communication may be > > confidential. > > You should only read, disclose, re-transmit, copy, distribute, act in > > reliance > > on or commercialise the information if you are authorised to do so. If > > you are not > > the intended recipient of this email communication, please notify us > > immediately by > > email to [email protected] or reply by email direct to > the > > sender and > > then destroy any electronic or paper copy of this message. Any views > > expressed in > > this email communication are those of the individual sender, except > > where the sender > > specifically states them to be the views of Wridgways The > Removalists.? > > Any personal > > information in this email must be handled in accordance with the > > Privacy Act 1988 > > (Cth). Wridgways The Removalists does not represent, warrant or > > guarantee that the > > integrity of this communication has been maintained nor that the > > communication is > > free of errors, virus or interference. > > > ####################################################################### > > ############## > > > > > > -- > > To unsubscribe send an email with subject unsubscribe to > > [email protected]. > > Please contact [email protected] for questions. > > -- > To unsubscribe send an email with subject unsubscribe to [email protected]. > Please contact [email protected] for questions. > > ##################################################################################### > This e-mail message has been scanned for Viruses and Content and cleared > by NetIQ MailMarshal > > ##################################################################################### > > > ##################################################################################### > The information contained in this email communication may be confidential. > You should only read, disclose, re-transmit, copy, distribute, act in > reliance > on or commercialise the information if you are authorised to do so. If you > are not > the intended recipient of this email communication, please notify us > immediately by > email to [email protected] or reply by email direct to the > sender and > then destroy any electronic or paper copy of this message. Any views > expressed in > this email communication are those of the individual sender, except where > the sender > specifically states them to be the views of Wridgways The Removalists. Any > personal > information in this email must be handled in accordance with the Privacy > Act 1988 > (Cth). Wridgways The Removalists does not represent, warrant or guarantee > that the > integrity of this communication has been maintained nor that the > communication is > free of errors, virus or interference. > > ##################################################################################### > > -- > To unsubscribe send an email with subject unsubscribe to [email protected]. > Please contact [email protected] for questions. > -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
