If you stop mythbackend, remove the file and restart, does the same behavior happen? I'm wondering if it's only happening because of "existing" files.
The syntax looks correct according to http://rsyslog.com/doc/rsconf1_fileowner.html -- You received this bug notification because you are a member of Mythbuntu Bug Team, which is subscribed to Mythbuntu. https://bugs.launchpad.net/bugs/904099 Title: rsyslog configuration not working Status in Mythbuntu, Ubuntu derivative focused upon MythTV: New Bug description: I am running the nightly master builds currently at 2:0.25.0~master.20111213.72d4370-0ubuntu0mythbuntu2 At some point the logging for the backend in the mythbuntu packages was changed to use syslog together with an rsyslogd configuration stanza: ---- cut ---- $FileOwner mythtv $FileGroup mythtv $FileCreateMode 0644 $DirOwner mythtv $DirGroup mythtv $DirCreateMode 0755 $template mythtvFile,"/var/log/mythtv/%programname%.log" local7.* ?mythtvFile & ~ ---- cut ---- This is not working as I think you expect it should be working. Specifically, the log files being created by rsyslogd are not owner.group mythtv.mythtv: -rw-r--r-- 1 syslog syslog 3456 2011-12-14 00:25 mythbackend.log Of course, I had to make the containing directory (/var/log/mythtv/) permissive to creating files with such ownership. To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/904099/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mythbuntu-bugs Post to : [email protected] Unsubscribe : https://launchpad.net/~mythbuntu-bugs More help : https://help.launchpad.net/ListHelp
