Opened 9 years ago

Closed 5 years ago

#1082 closed defect (wontfix)

log file isn't created when running bind10 with -u

Reported by: jinmei Owned by:
Priority: medium Milestone: Remaining BIND10 tickets
Component: logging Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: Medium
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 0.0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


If I started BIND10 with '-u bind' with logging configuration for
dumping logs to file:

Logging/loggers[0]/output_options[0]/destination	"file"	string	
Logging/loggers[0]/output_options[0]/output	"/home/jinmei/opt/var/log/bind10.log"	string	
Logging/loggers[0]/output_options[0]/flush	false	boolean	(default)
Logging/loggers[0]/output_options[0]/maxsize	100000	integer	
Logging/loggers[0]/output_options[0]/maxver	5	integer

The file was not created and I saw this message from liblog4cplus:

log4cplus:ERROR Unable to open file: /home/jinmei/opt/var/log/bind10.log

(seeing this is bad IMO, but it's a separate issue. See #1081).

Even though the directory is writable for the user of "bind":

drwxrwxr-x  2 jinmei  bind  512 Jun 29 15:01 /home/jinmei/opt/var/log

If I started BIND 10 without -u bind 10 and with root permission, it created
the bind10.log file. If I then changed the owner of the file to "bind",
this file is updated with new logs.

These are very strange and inconvenient.


Change History (4)

comment:1 Changed 9 years ago by shane

  • Defect Severity changed from N/A to Medium
  • Milestone changed from New Tasks to Year 3 Task Backlog

comment:2 Changed 8 years ago by shane

  • Milestone Year 3 Task Backlog deleted

Looks like we invoke setuid() but we never call setgid() from the boss:

        if self.__uid is not None:
  , self.__uid)

comment:3 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:4 Changed 5 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to bind10-old
Note: See TracTickets for help on using tickets.