Hitting a weird bug with the initd script that manages memcached in .08beta2 Whenever the file /etc/init.d/memcached is open in vim, I can stop the memcached service, but not restart it or start it. I played with it a bit and got the following Code: # Memcached running; admin stats page connects successfully. # Open /etc/init.d/memcached in vim. Without exiting vim, run the following: [root@cloud1 ~]# service memcached status Memcached server is running # stats page still connecting [root@cloud1 ~]# service memcached stop Memcached server stopped # stats page stops connecting [root@cloud1 ~]# service memcached status Memcached server is running # but it's not, I just stopped it, plus the stats page can't connect [root@cloud1 ~]# service memcached start Memcached server already running # no it's not [root@cloud1 ~]# service memcached status Memcached server is running # not it's not [root@cloud1 ~]# service memcached restart Memcached server stopped Memcached server already running # still not running # Close the init.d script in vim [root@cloud1 ~]# service memcached status Memcached server not running # now it correctly sees it's not running [root@cloud1 ~]# service memcached restart Memcached server already stopped # contrast with above, here it realizes it's not running Memcached server started # now it successfully boots I'm guessing opening the file in vim causes Linux to lock something somewhere that is preventing the status function in this script from realizing that memcached is actually stopped. So when I call `restart` or `start`, it checks the memcached status before trying to restart it, gets a report that memcached is already running (even though it's not), and exits without actually starting memcached. Any ideas how to fix the function that checks whether memcached is currently running? Normally wouldn't bother me, but this is causing my Ansible playbooks to report they've succeeded when in fact memcached is still stopped. I've got one Ansible task that edits the file, followed by another that restarts memcached. The second one is reporting success, but when I manually check memcached, it's stopped--again, I'm guessing the restart function stopped memcached, checked status, said "oh, it's already running" and exited without trying to start memcached.