[ATrpms-users] Mythtv 0.21-177 from 175: easy upgrade on Centos with improvement seen.

[john bray]

On Tue, 2008-02-26 at 22:10 +1100, Jean-Yves Avenard wrote:
> Hi again
> 
> On Tue, Feb 26, 2008 at 4:22 PM, Jean-Yves Avenard <jyavenard at gmail.com> wrote:
> >  177 introduced this new issue of the mythbackend not writing into the
> >  default log file.
> 
> Ben, my apologies, you were right. The issue did happen because
> mythbackend is now started as user mythtv and the log file was owned
> by root.
> 
> Once the permissions were fixed that issue disappeared.
> 
> Now, the problem is when not running as root, mythbackend can not
> access the DVB interface. Need to add udev rules so it the permissions
> will automatically be changed.

actually, i think it's more than just udev.  the console perms affect a
bunch of devices when someone logs in.  the numbering in
the /etc/console.perms.d directory is the opposite of the udev
directory.  i.e. you have to choose a HIGHER number than the defaults in
order to override it. (that sucks, doesn't it).

i attached the file from console.perms.d that i've kludged up for
several years now as an example of one that works.  it's not pretty.
fair warning.

john
-- 
cleverly disguised as a responsible adult.
-------------- next part --------------
# below is original stuff i put in from fc4 notes.  following it is
# the stuff i took from junior's live stuff in f7 that keeps myth
# working....
#
# device classes -- these are shell-style globs
#<v4l>=/dev/video* /dev/radio* /dev/winradio* /dev/vtx* /dev/vbi* \
#	/dev/video/* /dev/dvb/adapter*/*

# permission definitions
#<console>  0666 <v4l>        0666 root

# here begins the local.perms from junior as of Sat Nov 17 19:51:23 CST 2007
#
# jmb notes:
# 	- video and sound stuff is mostly for solving the mythbackend
# 	access when console user owns the device.
#
#	- sound - this will likely have to be the same as video since some
#	of the cards are wintv go cards what have to be audio'ed through
#	line in.
#
#	- scanner stuff is for adding sg0 to the perms to pick up the
#	linotype which, at least now, is the only sg device.
#	theoretically, it doesn't need different perms since it won't get
#	shared.
#
#	note that my current understanding is that, based on the man page
#	for pam_console_apply, that the naming convention is the reverse
#	from that of the udev .rules files.  apparently the console perms
#	files are read in lexical order like the udev files.  BUT, later
#	defs *>replace<* prior ones.  stupid convention.  might make sense
#	since this is likely parsed once at boot, and the other is probably
#	parsed at device creation time.  pah.  don't believe that either,
#	since it's likely parsed only at udev start time as well.  just
#	sucks as a convention.  but udevstart will force a rescan of the
#	udev stuffies.  mebbe this console.perms stuff happens at login?
#

# device classes -- these are shell-style globs
<v4l>=/dev/video* /dev/radio* /dev/winradio* /dev/vtx* /dev/vbi* \
      /dev/video/* /dev/dvb/adapter*/*

<sound>=/dev/dsp* /dev/audio* /dev/midi* \
        /dev/mixer* /dev/sequencer \
        /dev/sound/* /dev/beep \
        /dev/snd/*

<scanner>=/dev/scanner* /dev/usb/scanner* /dev/sg*

# permission definitions
<console>  0666 <v4l>        0666 root
<console>  0666 <sound>      0666 root
<console>  0666 <scanner>    0666 root