I meant "chown --quiet" of course. Now, for permissions, AFAICS syslogd starts up and creates the files as root, so that should not be a problem. According to the man page, it only needs write access as "syslog" user if it is HUP restarted, in which case it runs the same code but under another uid. Nice.
The "syslog" user is not in the "adm" group, and at the moment I am not sure why those files must be "syslog:adm". Furthermore, the files are created root:adm in the postinst. I would suggest: 1) Create /var/log/news in the init file and not in the postinst. This is the only subdir sysklog uses itself. 2) Fix syslogd to set file owner on file creation. 3) Remove file creation and chown from init file and postinst. Regarding (2) the current code just opens the file for append, so it does not change the owner of an existing file. If we want to preserve this behaviour, we'll need know if the file is newly created before chown'ing it. If not, this debdiff is one simple way of doing it. This is just a first take for the discussion, it adds -U and -G options that will chown all files opened to the uid/gid of the process. ** Attachment added: "sysklogd_1.5-5ubuntu4.debdiff2" http://launchpadlibrarian.net/21602895/sysklogd_1.5-5ubuntu4.debdiff2 -- Non-existent log files cannot be chown'ed https://bugs.launchpad.net/bugs/290127 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
