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 :-
On Fri, Dec 09, 2005 at 10:48:49AM +, 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 th
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 provid
On Thu, Dec 08, 2005 at 09:13:00AM +, 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?
> >>Wh
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 ;-)
Chr
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
> >> section) with the "daemon control socket (set in in the
> >> ze
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
> Tres Seaver wrote:
>
>> You have confused the "server socket" (which is set in the
>> section) with the "daemon control socket (set in in the
>> zeo.conf file; not currently settable in zope.conf). The control
>> socket has
Tres Seaver wrote:
You have confused the "server socket" (which is set in the
section) with the "daemon control socket (set in 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
-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
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
-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
11 matches
Mail list logo
