Okay, here's my thoughts (not a review) of the movie, The Quarrel. It's based on a play by Joseph Telushkin. At first, it just seems to be two guys, separated when they were 20 because of the Shoah, and one became a Yeshiva rabbi, and the other an atheistic writer. They find each other at a park, and they end up discussing, arguing, debating.
To me, it was really engaging. I loved how they really had depth, emotion. They interacted, and I really felt that the actors really were their characters. They are so passionate about their beliefs. They quarrel. But even when they are angry with one another, they stop just before it is too late, recognize that they are family, calm down, and start discussing again. They discuss Hitler, the future of Klal Yisrael, tolerance, Orthodoxy vs. Reason, even their relationship with each other, even over those years that each thought the other gone or dead.
But I must think: wow.. What a movie. I must show this to my kids when they are old enough. It's subtle weaving, it speaks to the soul of life, real lives, not some perfect lives owned by most characters, but lives filled with mistakes, regrets, and still plenty of mornings. I think I plan to purchase a copy of this (I netflix'ed it). Definitely one to add to my collection.. This movies definitely moves me.
Tuesday, August 30, 2005
Wednesday, August 10, 2005
Aha! Reverse proxying OWA (Exchange's web access) and RPC-over-HTTP using Apache 2.
This blog is informative for those of us running Exchange 2003 servers. If you don't, feel free to ignore it.
I finally figured out a way to reverse proxy Exchange's Outlook Web Access (OWA) as well as the RPC-over-HTTP thing that Outlook and Exchange 2003 can do using Apache 2. Some of this came from http://3cx.org/item/46#rpcoverhttp, although that method had more stuff than I needed in my vhost. I've put what I think is the bare minimum here. You put this into a < VirtualHost > area.
Also, note, that your INTERNET facing DNS needs to think that this box resolves as the SAME NAME as the real exchange server. So, let's say you have a server, LEMON.domain.com, which is a real Exchange 2003 server, and BLUE.domain.com, which is an Apache 2 box. You'll setup the internet-facing DNS to resolve LEMON.domain.com to the same IP as BLUE.domain.com. Then, BLUE needs to resolve the REAL LEMON.domain.com correctly (either by having your own internal DNS (which you probably have) or using hosts entries and the like).
Ex:
Internet:
LEMON.domain.com. IN A 1.2.3.4 ; fake lemon, blue is the reverse proxy for lemon
BLUE.domain.com. IN A 1.2.3.4
Inside (or in hosts file on BLUE):
LEMON.domain.com. IN A 1.2.3.156 ; the REAL lemon
Then setup a VHOST with this inside:
SSLEngine on
SSLProxyEngine on
# Server Certificate:
SSLCertificateFile /path/to/public.key
# Server Private Key:
SSLCertificateKeyFile /path/to/private.key
SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown
ProxyPass /Public https://real.exchange.server/public
ProxyPassReverse /Public https://real.exchange.server/public
ProxyPass /public https://real.exchange.server/public
ProxyPassReverse /public https://real.exchange.server/public
ProxyPass /exchange https://real.exchange.server/exchange
ProxyPassReverse /exchange https://real.exchange.server/exchange
ProxyPass /Exchange https://real.exchange.server/exchange
ProxyPassReverse /Exchange https://real.exchange.server/exchange
ProxyPass /Exadmin https://real.exchange.server/exadmin
ProxyPassReverse /Exadmin https://real.exchange.server/exadmin
ProxyPass /exadmin https://real.exchange.server/exadmin
ProxyPassReverse /exadmin https://real.exchange.server/exadmin
ProxyPass /ExchWeb https://real.exchange.server/exchweb
ProxyPassReverse /ExchWeb https://real.exchange.server/exchweb
ProxyPass /exchweb https://real.exchange.server/exchweb
ProxyPassReverse /exchweb https://real.exchange.server/exchweb
# Note: we don't use ProxyPass for /rpc, as it doesn't seem to work right
RewriteEngine On
RewriteRule ^(.*)/rpc/(.*) https://real.exchange.server/rpc/$2 [P]
That's what I'm using at my work.
I finally figured out a way to reverse proxy Exchange's Outlook Web Access (OWA) as well as the RPC-over-HTTP thing that Outlook and Exchange 2003 can do using Apache 2. Some of this came from http://3cx.org/item/46#rpcoverhttp, although that method had more stuff than I needed in my vhost. I've put what I think is the bare minimum here. You put this into a < VirtualHost > area.
Also, note, that your INTERNET facing DNS needs to think that this box resolves as the SAME NAME as the real exchange server. So, let's say you have a server, LEMON.domain.com, which is a real Exchange 2003 server, and BLUE.domain.com, which is an Apache 2 box. You'll setup the internet-facing DNS to resolve LEMON.domain.com to the same IP as BLUE.domain.com. Then, BLUE needs to resolve the REAL LEMON.domain.com correctly (either by having your own internal DNS (which you probably have) or using hosts entries and the like).
Ex:
Internet:
LEMON.domain.com. IN A 1.2.3.4 ; fake lemon, blue is the reverse proxy for lemon
BLUE.domain.com. IN A 1.2.3.4
Inside (or in hosts file on BLUE):
LEMON.domain.com. IN A 1.2.3.156 ; the REAL lemon
Then setup a VHOST with this inside:
SSLEngine on
SSLProxyEngine on
# Server Certificate:
SSLCertificateFile /path/to/public.key
# Server Private Key:
SSLCertificateKeyFile /path/to/private.key
SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown
ProxyPass /Public https://real.exchange.server/public
ProxyPassReverse /Public https://real.exchange.server/public
ProxyPass /public https://real.exchange.server/public
ProxyPassReverse /public https://real.exchange.server/public
ProxyPass /exchange https://real.exchange.server/exchange
ProxyPassReverse /exchange https://real.exchange.server/exchange
ProxyPass /Exchange https://real.exchange.server/exchange
ProxyPassReverse /Exchange https://real.exchange.server/exchange
ProxyPass /Exadmin https://real.exchange.server/exadmin
ProxyPassReverse /Exadmin https://real.exchange.server/exadmin
ProxyPass /exadmin https://real.exchange.server/exadmin
ProxyPassReverse /exadmin https://real.exchange.server/exadmin
ProxyPass /ExchWeb https://real.exchange.server/exchweb
ProxyPassReverse /ExchWeb https://real.exchange.server/exchweb
ProxyPass /exchweb https://real.exchange.server/exchweb
ProxyPassReverse /exchweb https://real.exchange.server/exchweb
# Note: we don't use ProxyPass for /rpc, as it doesn't seem to work right
RewriteEngine On
RewriteRule ^(.*)/rpc/(.*) https://real.exchange.server/rpc/$2 [P]
That's what I'm using at my work.
Tuesday, August 09, 2005
Solaris 10 Note
If you've screwed up your Solaris 10 setup by removing SUNWwbsup and you can't use pkgrm/pkgadd/etc. anymore, try this:
From disk 1, copy Solaris_10\Product\SUNWwbsup\Archive\none.bz2 to a temp directory
bunzip2 none.bz2
mv none.bz2.out none.cpio (ah hah!, file IS useful...)
cd /
cat /tmp/none/bz2.out | cpio -i -d
Then you can now run pkgadd and friends. The exercise is left to the reader on how to convince pkginfo and friends that said package has actually been installed again (I'd love to know, but don't care).
I messed up all of my zones today because I removed all unnecessary packages (and, it seems, at least one necessary one...) I've heard tell that this website has some good ideas on what's safe to remove or not.
From disk 1, copy Solaris_10\Product\SUNWwbsup\Archive\none.bz2 to a temp directory
bunzip2 none.bz2
mv none.bz2.out none.cpio (ah hah!, file IS useful...)
cd /
cat /tmp/none/bz2.out | cpio -i -d
Then you can now run pkgadd and friends. The exercise is left to the reader on how to convince pkginfo and friends that said package has actually been installed again (I'd love to know, but don't care).
I messed up all of my zones today because I removed all unnecessary packages (and, it seems, at least one necessary one...) I've heard tell that this website has some good ideas on what's safe to remove or not.
Monday, August 08, 2005
ADODB
I hate microsoft. I spent 3 hours this morning trying to figure out why a stored procedure would not execute, and kept blaming one of the parameters as being OUTPUT when it should be INPUT. And it was the wrong one. I finally noticed that my code all uses adoCmd.namedParameters = true, and Dmitriy's didn't. I set it, and it worked. Grrrr... I was ready to throttle someone over that. I mean, ADO could have said, "Hey, this is SQL Server, he's giving me @Names for the procedures, I'll bet he's using named sprocs!". But nooo. Way too much stress over this.
Sunday, August 07, 2005
Moose trip
My father-in-law and my brother-in-law (
Wednesday, August 03, 2005
What file extension am I? An EXE? Are you nuts?
border="0" alt="You are .exe When given proper orders, you execute them flawlessly. You're familiar to most, and useful to all.">
Which File Extension are You?
I disagree with this. I'm not an .exe. I'm a .so. A library for non-Windows users..
Subscribe to:
Posts (Atom)