-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Jakob,

I got to #162 a little earlier than I was expecting, it should no longer try to connect to the caldavd-pydir.sock with ProcessType=Combined and MultiProcess/ProcessCount=1.

So the stock config with a single processor should work fine after an SVN up.

But you say you're on a Dual P3? So the default config should have started you up in multiprocess mode. I see from your previous logfile that getNCPU executed fine, it just only found one processor. Are you running an SMP kernel? What kernel version are you using? What libc version? Can you show me /proc/cpuinfo? I'd like to make sure getNCPU supports as many platforms as possible.

Thanks,
- -David

On Apr 24, 2007, at 11:44 AM, Jakob Lenfers wrote:

David Reid schrieb:

Sorry for the inconvenience, and thanks for your interest.  This is a
known bug with uniprocessor mode
http://trac.macosforge.org/projects/calendarserver/ticket/162

Thanks for the software, I'm sure it'll work out great! :-)

Hopefully I will have time to resolve it this afternoon.

Until then you can work around it by setting ProcessType to "Single" in
the config file.

I've changed the entry in conf/caldavd-dev.plist:
<key>ProcessType</key>
<string>Single</string>

Sadly its still the same problem. I guess I forgot some information in
my first email:

I'm using linux with Python 2.4.4c1 on an old dual cpu P3. Is there
anything else that could help pinpointing the problem?

TIA, Jakob

_______________________________________________
calendarserver-users mailing list
calendarserver-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/calendarserver-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFGLmYNrsrO6aeULcgRAl/6AKCG+H4zF5wxh6bGLgE2vt0ok5Xx7ACgjjW3
ZKgY13C4SKvSeeM+01uGHC8=
=kQUp
-----END PGP SIGNATURE-----
_______________________________________________
calendarserver-users mailing list
calendarserver-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/calendarserver-users

Reply via email to