[mythtv-users] Mythfrontend fails if mythtv installed after user mythtv created

[James Abernathy]

On Sat, Jun 22, 2024 at 12:38 AM Hika van den Hoven <hikavdh at gmail.com>
wrote:

> Hoi Mike,
>
> Saturday, June 22, 2024, 1:00:21 AM, you wrote:
>
>
>
>
> > On Fri, Jun 21, 2024, 16:06 James Abernathy <jfabernathy at gmail.com>
> wrote:
>
>
>
>
>
> > The Security Pin defaults in the browser setup to 0000 and I leave it
> alone.
>
>
>
> > However, by creating the broken symlink you made your user unable
> > to write any changes to config.xml - the file the link pointed to
> > could not be accessed by 'jim' due to aforementioned umask on new
> > user homedir defaults. Removing step 7 altogether would allow the
> > default pin of 0000 and mythfrontend to create a new config.xml
> > entirely separate from the mythtv user's.
>
>
> > As to rebooting.  That comes from 40 years of knowing that it fixes
> > things that it shouldn't but does. This was true on the IBM 360
> > mainframe, the GE 4020, and the Windows PC.  So if all else fails reboot.
>
>
>
>
> > Rebooting leaves one to suspect that default processes upon boot
> > somehow alter the state beneficially, but not entirely understand what
> the changes are.
>
>
> > In some cases, operating systems with bugs like DOS-era Windows
> > leave the system intrinsically unstable after a period of leaking
> > resources etc.  Bugs you cannot fix require a reboot.
>
>
> > In other cases, like here, there is likely either nothing needed or
> > something very simple needed to get the system to a state which you
> expect,
>
>
> > Starting by clearly defining your expectations and observing the
> > results of testing what is needed to achieve them, may remove the
> > reflex of a reboot once the underlying processes involved become
> > clearer as the expectations are brought out in the open, perhaps
> > overriding some preconceptions in the process.
>
>
> > Mike
>
> I agree in essence with Mike in his assessment of the cause.
> If you want to share documents between users, put them in a communal
> accessible place and manage the access through a communal group. In
> this case /etc/ or /etc/mythtv/ as the location and mythtv as the
> group. Next create links for al the users to the file in their own
> home directory. You even can manage the creation of the link in the
> user creation configuration. Do not change the rights in the
> individual home directories to include group rights. It could in the
> long run create unexpected and unwanted side effect.
> That's the linux way!
>
> Tot mails,
>   Hika                            mailto:hikavdh at gmail.com
>
> "Zonder hoop kun je niet leven
> Zonder leven is er geen hoop
> Het eeuwige dilemma
> Zeker als je hoop moet vernietigen om te kunnen overleven!"
>
> De lerende Mens
>


I would not argue one way or the other on file/directory permissions.  I'm
not qualified.

However, it seems that installing v34 using the Web app does it right if
you don't create your 'mythtv' user/group ahead of time.

If you want/need the mythtv gid/uid to be a particular value, then the
config.xml in the user's, running Web App, home needs to be set up
correctly so that mythfrontend will run.

For me the easiest process is to copy the system file
/etc/mythtv/config.xml to the user's .mythtv/config.xml.

I created my testing VM with the btrfs file system so I can restore it just
before I create the mythtv user and install the software so it's a quick
restore of a snapshot and reboot. I'll test some different methods to see
if one is better than the other.

Jim A
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20240622/e24a6817/attachment-0001.htm>