On Sun, Dec 04, 2005 at 11:32:15AM +0100, Andreas Jung wrote:
WHY?
Because 'zdsock' is not an acceptable name. I am running on OS/2 and the path name must start with '\\socket\\'.
--On 4. Dezember 2005 10:26:03 +0000 John Poltorak <jp@warpix.org> wrote:
On Sun, Dec 04, 2005 at 11:13:29AM +0100, Andreas Jung wrote:
At the top of sample.conf it says
# Sample config file for zdctl.py and zdrun.py (which share a schema).
This sounds like something other than zope.conf.
Is there a real need for you to touch the configuration. Also as very advanced Zope user I've never had the need to touch this configuration for any reason. So what are your reasons?
I need to change the name of the socket.
-aj
-- John
-- John
--On 4. Dezember 2005 10:47:43 +0000 John Poltorak <jp@warpix.org> wrote:
On Sun, Dec 04, 2005 at 11:32:15AM +0100, Andreas Jung wrote:
WHY?
Because 'zdsock' is not an acceptable name.
I pass. OS/2 is ancient and also no longer supported by IBM. -aj
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John Poltorak wrote:
On Sun, Dec 04, 2005 at 11:32:15AM +0100, Andreas Jung wrote:
WHY?
Because 'zdsock' is not an acceptable name.
I am running on OS/2 and the path name must start with '\\socket\\'.
Johh, you are likely going to have to hack the 'socket-name' key into $SOFTWARE_HOME/lib/python/Zope2/zopeschema.xml (as a top-level option, I think, bound to 'sockname'; it might need to be a sub-option of 'zoperunner'). Please submit a patch (to http://www.zope.org/Collectors/Zope) when you get it working. Tres - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDkvoF+gerLs4ltQ4RAk3CAJ94XslX9sOw6VmcC2JDaooIXmotmACgtP5X ymxZAWD9nZn3ZmoetoV/DhE= =IhnZ -----END PGP SIGNATURE-----
On Sun, Dec 04, 2005 at 09:15:34AM -0500, Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
John Poltorak wrote:
On Sun, Dec 04, 2005 at 11:32:15AM +0100, Andreas Jung wrote:
WHY?
Because 'zdsock' is not an acceptable name.
I am running on OS/2 and the path name must start with '\\socket\\'.
Johh, you are likely going to have to hack the 'socket-name' key into $SOFTWARE_HOME/lib/python/Zope2/zopeschema.xml (as a top-level option, I think, bound to 'sockname'; it might need to be a sub-option of 'zoperunner').
Tres, Do you mean ? $SOFTWARE_HOME/lib/python/Zope2/Startup/zopeschema.xml That is the location of such a file on my system. As for hacking schema's that is something I'm not familiar with so I might need a little hand holding before I manage to apply the change you suggest. <sectiontype name="zoperunner"> <description> This section describes the options for zopectl. These options ... options, the command line option (short and long form) are given here too. </description> <multikey name="program" required="no"> <description> The program(s) that will be run by the runner </description> </multikey> <key name="daemon" datatype="boolean" required="no" default="true"> <description> Command-line option: -d or --daemon. .... - call umask(022) </description> </key> How exactly do I hack the 'socket-name' key into the file? Would the file $SOFTWARE_HOME/lib/python/zdaemon/sample.conf be of any use in this matter?
Please submit a patch (to http://www.zope.org/Collectors/Zope) when you get it working.
It may take some time to get working...
Tres - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDkvoF+gerLs4ltQ4RAk3CAJ94XslX9sOw6VmcC2JDaooIXmotmACgtP5X ymxZAWD9nZn3ZmoetoV/DhE= =IhnZ -----END PGP SIGNATURE-----
John Poltorak wrote:
Because 'zdsock' is not an acceptable name.
I am running on OS/2 and the path name must start with '\\socket\\'.
Oooo, ow, that's gonna hurt... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Mon, Dec 05, 2005 at 08:50:30AM +0000, Chris Withers wrote:
John Poltorak wrote:
Because 'zdsock' is not an acceptable name.
I am running on OS/2 and the path name must start with '\\socket\\'.
Oooo, ow, that's gonna hurt...
Zope itself works fine when started via runzope, so what is the problem in trying to provide an alternate socket name? zdctl is supposed to accept an alternative socket name:- -s/--socket-name SOCKET -- Unix socket name for client (default "zdsock") Unfortunately, I can't figure out any way to make use of this option.
Chris
-- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-- John
John Poltorak wrote:
Zope itself works fine when started via runzope, so what is the problem in trying to provide an alternate socket name?
zdctl is supposed to accept an alternative socket name:-
-s/--socket-name SOCKET -- Unix socket name for client (default "zdsock")
Unfortunately, I can't figure out any way to make use of this option.
Why do you care about this? AGAIK, this is only to do with those weird unix file-like socket things, and shouldn't be worried about if you're using a normal tcp socket as you should be ;-) cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Tue, Dec 06, 2005 at 09:51:12AM +0000, Chris Withers wrote:
John Poltorak wrote:
Zope itself works fine when started via runzope, so what is the problem in trying to provide an alternate socket name?
zdctl is supposed to accept an alternative socket name:-
-s/--socket-name SOCKET -- Unix socket name for client (default "zdsock")
Unfortunately, I can't figure out any way to make use of this option.
Why do you care about this? AGAIK, this is only to do with those weird unix file-like socket things, and shouldn't be worried about if you're using a normal tcp socket as you should be ;-)
According to the docs it should be possible to specify an alternate socket name. I am unable to use the name 'zdsock' so would like to configure Zope to use a user specific socket name. Either it is possible or it isn't. So far no one has told me how I can use what are supposed to be existing features. I've even found a sample.conf which contains this <runner> # Harmless example program sleep 100 # Repeat the defaults backoff-limit 10 daemon True forever True socket-name zdsock exit-codes 0,2 # user has no default umask 022 directory . default-to-interactive True hang-around False </runner> but no one seems to know how/where this is can be used. What is the point in having features if no one knows how to use them?
cheers,
Chris
-- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-- John
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Withers wrote:
John Poltorak wrote:
Zope itself works fine when started via runzope, so what is the problem in trying to provide an alternate socket name?
zdctl is supposed to accept an alternative socket name:-
-s/--socket-name SOCKET -- Unix socket name for client (default "zdsock")
Unfortunately, I can't figure out any way to make use of this option.
Why do you care about this? AGAIK, this is only to do with those weird unix file-like socket things, and shouldn't be worried about if you're using a normal tcp socket as you should be ;-)
"Bzzzt! Thank you for playing!" ;) You have confused the "server socket" (which is set in the <http-server> section) with the "daemon control socket (set in <runner> in the zeo.conf file; not currently settable in zope.conf). The control socket has to be a Unix-domain socket. John is asking to surface an existing zdaemon feature (already used in zeo.conf) within zope.conf. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDlatH+gerLs4ltQ4RAvDmAJ9Bp7MmZHVYD/Z38/RCA0/LeEh0RgCfcMXN GRlLvjeQ7gYb3mOptTtA1oc= =Fb+L -----END PGP SIGNATURE-----
Tres Seaver wrote:
You have confused the "server socket" (which is set in the <http-server> section) with the "daemon control socket (set in <runner> in the zeo.conf file; not currently settable in zope.conf). The control socket has to be a Unix-domain socket. John is asking to surface an existing zdaemon feature (already used in zeo.conf) within zope.conf.
Ah, okay. How does this work on windows? What's wrong with the default name? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Withers wrote:
Tres Seaver wrote:
You have confused the "server socket" (which is set in the <http-server> section) with the "daemon control socket (set in <runner> in the zeo.conf file; not currently settable in zope.conf). The control socket has to be a Unix-domain socket. John is asking to surface an existing zdaemon feature (already used in zeo.conf) within zope.conf.
Ah, okay. How does this work on windows?
zdaemon / zopectl *don't* work on windows.
What's wrong with the default name?
Th the original poster's case, his OS requires that Unix-domain sockets have mangled names. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDlutj+gerLs4ltQ4RAic1AJ9wJJp10xx/HJnPbKaRYNHtM05VvACgmyem 6w5fCXtXVKkdbTLYLMPjgBU= =rhQt -----END PGP SIGNATURE-----
Tres Seaver wrote:
Ah, okay. How does this work on windows?
zdaemon / zopectl *don't* work on windows.
oh, my OS is broken *schniff*
What's wrong with the default name?
Th the original poster's case, his OS requires that Unix-domain sockets have mangled names.
...and so is his ;-) Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Thu, Dec 08, 2005 at 09:13:00AM +0000, Chris Withers wrote:
Tres Seaver wrote:
Ah, okay. How does this work on windows?
zdaemon / zopectl *don't* work on windows.
oh, my OS is broken *schniff*
Are you saying that Zope cannot be restarted through ZMI on Windows?
What's wrong with the default name?
Th the original poster's case, his OS requires that Unix-domain sockets have mangled names.
...and so is his ;-)
At the moment, the problem is being able to provide an alternative socket name via a command line parameter which is a feature that is supposed to be already provided by zdctl, but no one seems to know how it works, so I have no way of knowing whether it can be made to work on my OS or not.
Chris
-- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-- John
John Poltorak wrote:
Are you saying that Zope cannot be restarted through ZMI on Windows?
Who does that anyway? Even on unix, I use zopectl restart, my production zope stuff on windows is just scheduled tasks running from Task Scheduler...
At the moment, the problem is being able to provide an alternative socket name via a command line parameter which is a feature that is supposed to be already provided by zdctl, but no one seems to know how it works, so I have no way of knowing whether it can be made to work on my OS or not.
Well, I'm afraid that's how open source works. Yours is the itch, better get scratching ;-) Tres gave you some hints, in that basically you want to surface that ooption in zope.conf. Reading the code in the Zope.Startup package would be where I'd start, although I warn you it's a little contorted :-S cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Fri, Dec 09, 2005 at 10:48:49AM +0000, Chris Withers wrote:
John Poltorak wrote:
Are you saying that Zope cannot be restarted through ZMI on Windows?
Who does that anyway?
Even on unix, I use zopectl restart,
That is the point - zopectl uses a socket - 'zdsock'.
At the moment, the problem is being able to provide an alternative socket name via a command line parameter which is a feature that is supposed to be already provided by zdctl, but no one seems to know how it works, so I have no way of knowing whether it can be made to work on my OS or not.
Well, I'm afraid that's how open source works. Yours is the itch, better get scratching ;-)
Tres gave you some hints, in that basically you want to surface that ooption in zope.conf. Reading the code in the Zope.Startup package would be where I'd start, although I warn you it's a little contorted :-S
Well maybe you can explain what is the point of the '-s' flag or sample.conf. Is it meant to be helpful? I don't even see it mentioned in the documentation. Am I missing something?
cheers,
Chris
-- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-- John
John Poltorak wrote:
Are you saying that Zope cannot be restarted through ZMI on Windows?
Who does that anyway?
Even on unix, I use zopectl restart,
That is the point - zopectl uses a socket - 'zdsock'.
Oh right, well, no, you don't have that kind of socket on WIndoze as far as I know :-S
Tres gave you some hints, in that basically you want to surface that ooption in zope.conf. Reading the code in the Zope.Startup package would be where I'd start, although I warn you it's a little contorted :-S
Well maybe you can explain what is the point of the '-s' flag or sample.conf.
Never seen either I'm afraid...
Is it meant to be helpful?
I'm sure whoever their authors were thought so, but most likely in a context different to yours... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Wed, Dec 07, 2005 at 09:02:11AM -0500, Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Chris Withers wrote:
Tres Seaver wrote:
You have confused the "server socket" (which is set in the <http-server> section) with the "daemon control socket (set in <runner> in the zeo.conf file; not currently settable in zope.conf). The control socket has to be a Unix-domain socket. John is asking to surface an existing zdaemon feature (already used in zeo.conf) within zope.conf.
Ah, okay. How does this work on windows?
zdaemon / zopectl *don't* work on windows.
What's wrong with the default name?
Th the original poster's case, his OS requires that Unix-domain sockets have mangled names.
All I'm asking for at the moment is how to take advantage of what are supposed to be existing options of setting the socket name to something other than the default 'zdsock'. Presumably someone created the the '-s' option to zdctl for exactly this purpose.
Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDlutj+gerLs4ltQ4RAic1AJ9wJJp10xx/HJnPbKaRYNHtM05VvACgmyem 6w5fCXtXVKkdbTLYLMPjgBU= =rhQt -----END PGP SIGNATURE-----
-- John
participants (4)
-
Andreas Jung -
Chris Withers -
John Poltorak -
Tres Seaver