Package Details: tvheadend-git 4.3.r1428.gbef96c5d2-1

Git Clone URL: https://aur.archlinux.org/tvheadend-git.git (read-only)
Package Base: tvheadend-git
Description: TV streaming server for Linux
Upstream URL: https://tvheadend.org/
Licenses: GPL3
Conflicts: hts-tvheadend, hts-tvheadend-svn, tvheadend, tvheadend-git
Provides: tvheadend
Submitter: zman0900
Maintainer: zman0900
Last Packager: zman0900
Votes: 22
Popularity: 0.023638
First Submitted: 2015-08-10 20:59
Last Updated: 2018-10-04 17:43

Pinned Comments

luciferin commented on 2017-04-06 14:01

I started up a wiki page for Tvheadend. Input and help is welcome.

https://wiki.archlinux.org/index.php/Tvheadend

Latest Comments

1 2 3 4 5 6 ... Next › Last »

golodhrim commented on 2019-09-18 14:52

Can Somebody please remove the Out of Date Flag, cause it isn't and it is just annoying seeing it popup at every upgrade.

francoism90 commented on 2019-04-25 10:53

Why has this been flagged?

parkerlreed commented on 2019-04-15 23:36

@troydwill The comments here mention what needs to be done. The package isn't out of date.

mercora commented on 2019-04-15 05:07

it should be noted that Tvheadend runs with the "hts" user using this package. That means if you try to run it with the -C flag you need to make sure its running with the same user. TBH i think this should be the default.

"If no user account exists then create one with no username and no password. Use with care as it will allow world-wide administrative access to your Tvheadend installation until you create or edit the access control from within the Tvheadend web interface."

Arch packages never activate themselves on installation automatically like they do on Debian for example. So explicit action is required to have it exposed like described. The alternative is to create a superuser file in the configuration directory that looks like this:

{ "username": "supersuser", "password": "verysecurepassword" }

So you either do that prior to starting it or start with the first-run flag anyhow. I am not sure if the superuser config file still works when using this flag though, so that might need to be checked first to make the more paranoid people among us happy.

mrclrchtr commented on 2019-04-14 14:28

"If you build Tvheadend from source and just execute it, it won’t let anyone in."

https://tvheadend.org/projects/tvheadend/wiki/Faq

You need to start tvheadend with "-C" the first time.

troydwill commented on 2019-04-11 09:38

The administration web page at http://localhost:9981 after install is requiring a username and password. What are they?

mercora commented on 2019-03-18 11:45

to clarify this up for me i looked it up in the code and documentation. libsystemd as said is used to support systemd specific features like socket activation and a software watchdog in this case. While the socket activation appears as of not much use, at least to me, the software watchdog could be interesting in cases where the process just locks up somehow. The library is practically available on all arch installations so it might just as well could be enabled if desired :)

francoism90 commented on 2019-03-16 14:20

@mercora Thanks for the info! I wasn't aware why this flag existed, it indeed seems unwanted to be enabled. :)

mercora commented on 2019-03-16 10:18

i am pretty sure libsystemd is also used for socket activation which is not used in the current systemd unit file for this package either. It therefore should be safe to disable the dependency. If you want to enable this support there is a comment in the unit file about how to make use of these features.

zman0900 commented on 2019-03-14 23:22

It's been quite a while ago so I don't remember the details, but I did try that flag in the past. I don't remember for sure, but I don't think it worked.

From what I can see in the service file, it sounds like this just enables some watchdog feature of systemd?
https://github.com/tvheadend/tvheadend/blob/master/rpm/tvheadend.service

Does anyone has a use for this? I'm not opposed to enabling it, but I'd rather not do it without good reason since it appears to require changes to the service file too.