Hey, your English is better than my Spanish... :-)
Don't use tvheadend start.
Try this instead of
sudo su hts
and
tvheadend start@... while logged in as vicenj:
sudo service tvheadend start
(EDIT: sorry, I had to edit that - I'd got the command wrong originally!)
You should get a confirmation and it'll tell you what process ID the service has started as. You can confirm through @ps -eaf | grep tvheadend
- you should see
tvheadend -f -u hts -g video -s
or something very similar under that process ID (PID).
If you don't, try it the direct way:
sudo tvheadend -f -u hts -g video
... again, check using
ps -eaf@.
Every user on Linux has a username - such as vicenj - and one or more groups. Files then have user, group and other access rights. @ls -la
will show them: rwxr-xr-x is read/write/execute for user, and read/execute for group and other; you'll also see the file's user ownership and group ownership, so you know to whom these rights apply.
To access the tuners, the process needs to be running as the rightgroup, to access the config files, it needs to be running as the rightuser.
By starting it at the command line with
tvheadend@, you're running as the user who's starting the program - in this case, hts - but you're also running as the default group for that user. If that group isn't @video@, then you're likely to run into problems, because you'll be accessing the tuners as *other* and not *group* permissions. Make sense?
Typing @id
will tell you who you are - it will list the username and user ID number (UID - the numeric equivalent of username), the default group name and group id (GID), and any other group memberships that this user has. So, if user hts isn't a member of
video
by default, this command will tell you... try it, and post the results here if you like.
But starting tvheadend through one of the commands above is the way to go... I don't know why it's not automatically starting, though...