[Zope-dev] Zope options order sensitive
I'm just beginning my study of the zope source. Going through z2.py I noticed that order matters in specifying command line options. For instance: ./start -a 127.0.0.1 -P 8000 sets HTTP_PORT to: [('127.0.0.1', '8080')] but:./start -P 8000 -a 127.0.0.1 sets HTTP_PORT to: [('', '8080')] I'm not far enough along yet to know if this makes a difference in the end. Does it? Chris ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope options order sensitive
Not really... do you want to only listen on 127.0.0.1? - Original Message - From: "Chris Gray" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 19, 2001 3:43 PM Subject: [Zope-dev] Zope options order sensitive I'm just beginning my study of the zope source. Going through z2.py I noticed that order matters in specifying command line options. For instance: ./start -a 127.0.0.1 -P 8000 sets HTTP_PORT to: [('127.0.0.1', '8080')] but:./start -P 8000 -a 127.0.0.1 sets HTTP_PORT to: [('', '8080')] I'm not far enough along yet to know if this makes a difference in the end. Does it? Chris ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope options order sensitive
The example was fictional; the ips and ports have been changed to protect the guilty. I'm more interested in just understanding how the code works. It just struck me that given the way the server_info function works in z2.py that you could get a situation where you meant to have zope listening on only one address (specified with an -a option), but if options for particular ports are specified for a server, it will listen to that port for all addresses. An -a will have no effect on what is set by -m, -w, -W, -f, or -P if -a appears on the command line after them. ./start -f 21 -a special.zope.ip will set Zope listening only on the ip address special.zope.ip except it will be listening at _all_ addresses on the machine for ftp requests on port 21, which might not be the result the user intended. It is not the same as: ./start -f special.zope.ip:21 -a special.zope.ip Chris On Thu, 19 Apr 2001, Chris McDonough wrote: Not really... do you want to only listen on 127.0.0.1? - Original Message - From: "Chris Gray" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 19, 2001 3:43 PM Subject: [Zope-dev] Zope options order sensitive I'm just beginning my study of the zope source. Going through z2.py I noticed that order matters in specifying command line options. For instance: ./start -a 127.0.0.1 -P 8000 sets HTTP_PORT to: [('127.0.0.1', '8080')] but:./start -P 8000 -a 127.0.0.1 sets HTTP_PORT to: [('', '8080')] I'm not far enough along yet to know if this makes a difference in the end. Does it? Chris ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope options order sensitive
I understand. Congratulations! You've found your first bug! ;-) Can you file this with the Collector at http://classic.zope.org:8080/Collector ? - Original Message - From: "Chris Gray" [EMAIL PROTECTED] To: "Chris McDonough" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, April 19, 2001 4:21 PM Subject: Re: [Zope-dev] Zope options order sensitive The example was fictional; the ips and ports have been changed to protect the guilty. I'm more interested in just understanding how the code works. It just struck me that given the way the server_info function works in z2.py that you could get a situation where you meant to have zope listening on only one address (specified with an -a option), but if options for particular ports are specified for a server, it will listen to that port for all addresses. An -a will have no effect on what is set by -m, -w, -W, -f, or -P if -a appears on the command line after them. ./start -f 21 -a special.zope.ip will set Zope listening only on the ip address special.zope.ip except it will be listening at _all_ addresses on the machine for ftp requests on port 21, which might not be the result the user intended. It is not the same as: ./start -f special.zope.ip:21 -a special.zope.ip Chris On Thu, 19 Apr 2001, Chris McDonough wrote: Not really... do you want to only listen on 127.0.0.1? - Original Message - From: "Chris Gray" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 19, 2001 3:43 PM Subject: [Zope-dev] Zope options order sensitive I'm just beginning my study of the zope source. Going through z2.py I noticed that order matters in specifying command line options. For instance: ./start -a 127.0.0.1 -P 8000 sets HTTP_PORT to: [('127.0.0.1', '8080')] but:./start -P 8000 -a 127.0.0.1 sets HTTP_PORT to: [('', '8080')] I'm not far enough along yet to know if this makes a difference in the end. Does it? Chris ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope options order sensitive
Hmmm... perhaps an undocumented feature rather than a bug? Rereading the doc string I find the description of the -X option mentions a case of argument order making a difference; -X cancels preceding port options but not following ones. On Thu, 19 Apr 2001, Chris McDonough wrote: I understand. Congratulations! You've found your first bug! ;-) Can you file this with the Collector at http://classic.zope.org:8080/Collector ? - Original Message - From: "Chris Gray" [EMAIL PROTECTED] To: "Chris McDonough" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, April 19, 2001 4:21 PM Subject: Re: [Zope-dev] Zope options order sensitive The example was fictional; the ips and ports have been changed to protect the guilty. I'm more interested in just understanding how the code works. It just struck me that given the way the server_info function works in z2.py that you could get a situation where you meant to have zope listening on only one address (specified with an -a option), but if options for particular ports are specified for a server, it will listen to that port for all addresses. An -a will have no effect on what is set by -m, -w, -W, -f, or -P if -a appears on the command line after them. ./start -f 21 -a special.zope.ip will set Zope listening only on the ip address special.zope.ip except it will be listening at _all_ addresses on the machine for ftp requests on port 21, which might not be the result the user intended. It is not the same as: ./start -f special.zope.ip:21 -a special.zope.ip Chris On Thu, 19 Apr 2001, Chris McDonough wrote: Not really... do you want to only listen on 127.0.0.1? - Original Message - From: "Chris Gray" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, April 19, 2001 3:43 PM Subject: [Zope-dev] Zope options order sensitive I'm just beginning my study of the zope source. Going through z2.py I noticed that order matters in specifying command line options. For instance: ./start -a 127.0.0.1 -P 8000 sets HTTP_PORT to: [('127.0.0.1', '8080')] but:./start -P 8000 -a 127.0.0.1 sets HTTP_PORT to: [('', '8080')] I'm not far enough along yet to know if this makes a difference in the end. Does it? Chris ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )