Tell the admin to run "komrunning start" if upgrading.

README

@@ -178,16 +178,25 @@ AUTHORS			List of authors.
       program.  Most sane cron systems does so.  You may want to
       create a .forward file for user "lyskom".
 
-  11. Wait for updateLysKOM to start the server, or run updateLysKOM
+  11. If you are upgrading, you must run komrunning again to remove
+      the lock it created: 
+
+	$ su lyskom
+	$ /usr/lyskom/sbin/komrunning start
+
+      (Despite its name, this does not actually start lyskomd.  See
+      the next step.)
+
+  12. Wait for updateLysKOM to start the server, or run updateLysKOM
       manually (as user "lyskom").  You are ready.
 
-  12. Read the documentation in doc/lyskomd.info, especially the
+  13. Read the documentation in doc/lyskomd.info, especially the
       Administration chapter.  It tells you how to shut down and
       restart lyskomd.  LysKOM needs your attention once in a while.
       Here at Lysator we expunge old texts (with "dbck -g")
       approximately twice a year.
 
-  13. We would like to know about where LysKOM servers are running.
+  14. We would like to know about where LysKOM servers are running.
       If you start a server, please mail "kom@lysator.liu.se", and
       tell us that you are running a server.  (You are very welcome to
       tell more about you, but that's not necessary).