BIND 10 #711: starting to use --user

[BIND 10 Development]

#711: starting to use --user
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |  jinmei
            Priority:  medium        |                       Status:
           Component:  Boss of BIND  |  accepted
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20130108
         Sub-Project:  Core          |                   Resolution:
Estimated Difficulty:  3             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  High
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jinmei):

 trac711 is ready for review.

 This doesn't do exactly what was discussed
 http://bind10.isc.org/ticket/711#comment:7 but as I said in my
 previous comment I thought the real issue in this context is that it's
 not clear what was wrong (and what to do to fix it) when 'bind10 -u'
 fails due to a permission problem with the log lock file.

 Now it fails as follows:
 {{{
 INFO [b10-boss.boss]: BIND10_STARTING starting BIND10: bind10 20110223
 (BIND 10 20121219)
 ...
 INFO [b10-boss.boss]: BIND10_SOCKCREATOR_INIT initializing socket creator
 parser
 DEBUG [b10-boss.boss]: BIND10_STARTED_PROCESS_PID started b10-sockcreator
 (PID 91073)
 INFO [b10-boss.boss]: BIND10_SETGID setting GID to 4294967294
 ERROR [b10-boss.boss]: BIND10_COMPONENT_START_EXCEPTION component Socket
 creator failed to start: failed to change user: Unable to use interprocess
 sync lockfile (Permission denied):
 /Users/jinmei/opt/var/bind10/logger_lockfile
 ERROR [b10-boss.boss]: BIND10_COMPONENT_FAILED component Socket creator
 (pid 91073) failed: unknown condition
 FATAL [b10-boss.boss]: BIND10_COMPONENT_UNSATISFIED component Socket
 creator is required to run and failed
 ERROR [b10-boss.boss]: BIND10_CONFIGURATOR_PLAN_INTERRUPTED configurator
 plan interrupted, only 0 of 3 done
 INFO [b10-boss.boss]: BIND10_KILLING_ALL_PROCESSES killing all started
 processes
 INFO [b10-boss.boss]: BIND10_SEND_SIGKILL sending SIGKILL to Socket
 creator (PID 91073)
 WARN [b10-boss.boss]: BIND10_SOCKCREATOR_KILL killing the socket creator
 INFO [b10-boss.boss]: BIND10_SEND_SIGNAL_FAIL sending SIGKILL to Socket
 creator (PID 91073) failed: [Errno 1] Operation not permitted
 FATAL [b10-boss.boss]: BIND10_STARTUP_ERROR error during startup: failed
 to change user: Unable to use interprocess sync lockfile (Permission
 denied): /Users/jinmei/opt/var/bind10/logger_lockfile; TIP: if this is
 about permission error for a lock file, check if the directory of the file
 is writable for the user of the bind10 process; often you need to start
 bind10 as a super user.  Also, if you specify the -u option to change the
 user and group, the directory must be writable for the group, and the
 created lock file must be writable for that user. Finally, make sure the
 lock file is not left in the directly before restarting.
 }}}

 I don't think we need a changelog entry for this task.  In some sense
 it's user-visible, but it doesn't really solve a functionality defect
 or add a new feature.

-- 
Ticket URL: <http://bind10.isc.org/ticket/711#comment:16>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development