Memcached is started even though it is commented out in config file

[macosforgebot]

plaes@… originally submitted this as ticket:366

---

For some weird reason, memcache support is started even when no memcached configuration is present.

[macosforgebot]

john.holland@… originally submitted this as attachment:default-system-memcached.patch:⁠ticket:366

• Attachment default-system-memcached.patch (498 bytes) added

[macosforgebot]

john.holland@… originally submitted this as comment:1:⁠ticket:366

---

I see two possibilities:

• explicitly configure memcached not to start

    <key>Memcached</key>
    <dict>
      <dict>
         <key>Default</key>
         <dict>
            <key>ServerEnabled</key>
            <false/>
         </dict>
      </dict>
    </dict>

• default memcached to disabled

  ===================================================================
  --- twistedcaldav/stdconfig.py  (revision 6084)
  +++ twistedcaldav/stdconfig.py  (working copy)
  @@ -549,7 +549,7 @@
         "Pools": {
             "Default": {
                 "ClientEnabled": True,
  -                "ServerEnabled": True,
  +                "ServerEnabled": False,
                 "BindAddress": "127.0.0.1",
                 "Port": 11211,
                 "HandleCacheTypes": [

[macosforgebot]

@wsanchez originally submitted this as comment:2:⁠ticket:366

• Status changed from new to closed
• Resolution changed from to Behaves correctly

---

The default is to start memcached, so not configuring it otherwise won't change that default. This works as designed.

memcached is a required part of the service, so the default won't be changing any time soon.