Mettbrot

I understand, thank you! It seems strage throug that i have no possibility to access those files via the command line. Any idea how they get created? Since normally unraid seems to handle äüö just fine...

Hey! It seems that unraid has a Problem with special characters such as german umlauts äöü or frensh axon éáà. I had this probloem before on some files that sabnzbd created. This time it is present in my shares config files leading to a situation where the User Shares configuration page only shows an empty list: (I have no idea how these duplicates were created) root@Server:/boot/config/shares# ls Ablage.cfg* Aufnahmen.cfg* Downloads.cfg* Installation.cfg* Anwendungen.cfg* Bilder.cfg* Filme.cfg* Musik.cfg* Apps.cfg* Bücher.cfg* Hörbücher.cfg* Privat.cfg* Audio.cfg* B\374cher.cfg* H\366rb\374cher.cfg* Spiele.cfg* root@Server:/boot/config/shares# find . -type f ./Ablage.cfg ./Anwendungen.cfg ./Apps.cfg ./Audio.cfg ./Aufnahmen.cfg ./Bilder.cfg ./Bücher.cfg ./B?cher.cfg ./Downloads.cfg ./Filme.cfg ./Hörbücher.cfg ./H?rb?cher.cfg ./Installation.cfg ./Musik.cfg ./Privat.cfg ./Spiele.cfg root@Server:/boot/config/shares# find . -type f -iname "*cher*" ./Bücher.cfg ./Hörbücher.cfg Windows shows these files just as files with a blank name. 1. Why has unraid problems with these characters? 2. How can I sort this out? How can I rename the files? I have no chance to address them as neither 'B\374cher.cfg' nor 'B?cher.cfg' works. It seems this fellow has the same problem: http://lime-technology.com/forum/index.php?topic=42062.msg399672#msg399672 Thanks

Don't know if it helps but this was actually the first release since a long time that directly booted after the update. Prior I suffered from an issue described here: http://lime-technology.com/forum/index.php?topic=42800.msg409116#msg409116

Maybe some flavour of this? http://lime-technology.com/forum/index.php?topic=42800.msg409116#msg409116 I never figured it out when it works and when it doesn't. Each update I have to try several times...

I'm glad you like it :)

Just a quick note. I updated the tvh pack to the latest 4.0.7 version!

I released a new update with the latest and greatest stable TvHeadend version 4.0.6

The 6.1 Openelec bzroot file hangs for me at boot Loads the first three "dots" and is stuck there. I redownloaded a couple of times, still nothing. Anyone else having trouble with that file? Or what else could it be?

Hey I moved the rc script to /usr/local/emhttp/plugins/<plugin-name>/scripts/. An update should be available in the plugin manager. In the thread you linked Tom says it is recommended to just use /plugins/<plugin-name>/scripts/ and not the long form like you did in your sleep plugin (where I looked to adapt the location ). Doesn't this apply to rc scripts too? Thanks for the help.

If I find some time tomorrow I will push an update.

i think you confused this thread with the addon thread?

Hey! Does this include the changes made to the "official" preclear script by Joe L.? Your changelog is not clear about this As an additional request: The script should look for the readvz file in the same folder as the actual script is, for people who dont like their /boot/ to be filled

I don't know anything about hdhomerun tuners; i have never used them. BUT I know that support has recently been added to tvheadend itsself. This means they should work out of the box. There is a button "discover SAT>IP tuners" in tvheadend maybe you try that As CHBMB said maybe you'll need to configure the adapter first using a windows machine.

Hey everyone, I upgraded tvheadend to the latest stable version 4.0.5

I can imagine one for the future. But tvheadend just branched their repository for the 4.0 version. For the time being, stable and "unstable" are quite the same.

While warming up this topic tricked me to think it was a new poll, it yould in deed be interesting to see how many people run addons, now that docker and kvm seem to be mature in unRaid 6

This plugin installs a stable version of tvheadend, a TV streaming backend, on your unRaid machine. It supports DVB-S, DVB-S2, DVB-C, DVB-T, ATSC, IPTV, SAT>IP and HDHomeRun as input sources. Install it via the Plugin Page of unRaid's webGUI: https://raw.githubusercontent.com/Mettbrot/unRAID/master/tvheadend.plg In order to work correctly with an USB or PCI(e) tuner you may attach to your machine, you need to replace the bz* files on your flash drive with the ones provided by CHBMB here. Select your version and then 'libreelec'!. They contain the drivers needed to recognize your hardware. After installation you will find a tvheadend Icon in your settings. There you can see if your tuner has been recognized and installed properly. You should set the config directory to a persistent path (I recommend the cache drive), and finally set your superuser login and password under "advanced configuration". After it started you can reach the tvheadend configuration interface via http://tower:9981 where you use your superuser credentials to login. There is a setting to automatically wake up for recordings, which is explained in detail here. Shoutout to piotrasd and WW for their original work on this plugin and their help - it has come a long way! Please give me feedback on how it works for you. Thank you! Changelog: 2019.08.17a: Update plugin to remove warings on settings page 2019.02.27: Update to TvHeadend 4.2.8, 2018.12.13: Update to TvHeadend 4.2.7, remove conflicting dependency to libssl 2018.04.09: Update to TvHeadend 4.2.6 2018.01.14: add missing packages for 4.2.5 2018.01.04: update to TvHeadend 4.2.5-3 2017.11.06: update to TvHeadend 4.2.4-10 2017.08.02: update to TvHeadend 4.2.3 2017.04.29: updated to TvHeadend 4.2.1 STABLE 2016.05.11: update to TvHeadend 4.1-2409 2016.05.11: update to TvHeadend 4.1 PLEASE BACK UP YOUR DATABASE 2016.03.23: update to TvHeadend 4.0.9 2016.01.15: update to TvHeadend 4.0.8, fix loading of settings, add setting for wakeup script 2015.10.29: update to TvHeadend 4.0.7 2015.10.05: Implement missing policy parts and update to TvHeadend 4.0.6 2015.08.24: Adapt to Unraid 6.1 security policy 2015.06.25: TVheadend version 4.0.5 2015.06.09: Initial version. TVheadend version 4.0.4

I don't believe that is true, and as Frank showed, it's almost certain it's not true. Can you recall where you read that? If smb-extra.conf is working for you now in -rc6a, then it's unlikely to change in the final version. I agree!!! While there are probably less than fifty unRAID users who have a use for that file, those who do would be very knowledgeable and would need no support in using that feature. The only reason that it might be dropped is if Samba dropped support of the 'include' statement and I can't see that EVER happening!!! (I can remember that the 'include' statement was a part of the UNIX C compiler back in the early 1980's. It is an essential part of that language which saves uncalculable amounts of time in writing programs!) EDIT: Plus, one could easily construct a smb.conf to add the line back in and save the file for the Flash drive. Then add the necessary commands into the go file to stop samba, copy this new file to the proper location, and restart Samba. Problem solved! I am quite sorry for all the noise. I actually read it as part of a post from you, RobJ which I completely missunderstood - I get that now :D I wan't really following the discussion but only read that last statement - bear with me Thank you all for the clarification!

Hey everyone. I read somewhere that smb-extra.conf has been ditched from newer releases. I use some options to get offline caching in Windows to work: [global] oplocks = yes level2 oplocks = yes kernel oplocks = no map archive = yes map system = yes map hidden = yes Where can I put those options now?

Haha, you had me there! I thought you copied the "403 Forbidden" page Can't wait for your next episode: about the most popular Error on the Internet! Just kidding, starting to watch NOW

Hey! Thanks for your response! I tried it again today and it still showed the two errors, but it started nevertheless... Strage thing It seems to work flawlessly now. root@Server:~# ldd /usr/bin/tvheadend /usr/bin/tvheadend: /lib64/libcrypto.so.1.0.0: no version information available (required by /usr/bin/tvheadend) /usr/bin/tvheadend: /lib64/libssl.so.1.0.0: no version information available (required by /usr/bin/tvheadend) linux-vdso.so.1 (0x00007ffea859b000) libdvbcsa.so.1 => /usr/lib64/libdvbcsa.so.1 (0x00002b597919e000) libssl.so.1.0.0 => /lib64/libssl.so.1.0.0 (0x00002b59793b1000) libcrypto.so.1.0.0 => /lib64/libcrypto.so.1.0.0 (0x00002b597961e000) libz.so.1 => /lib64/libz.so.1 (0x00002b59799fd000) liburiparser.so.1 => /usr/lib64/liburiparser.so.1 (0x00002b5979c12000) libavahi-common.so.3 => /usr/lib64/libavahi-common.so.3 (0x00002b5979e2b000) libavahi-client.so.3 => /usr/lib64/libavahi-client.so.3 (0x00002b597a037000) libdbus-1.so.3 => /usr/lib64/libdbus-1.so.3 (0x00002b597a247000) libdl.so.2 => /lib64/libdl.so.2 (0x00002b597a48d000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00002b597a691000) libm.so.6 => /lib64/libm.so.6 (0x00002b597a8ae000) librt.so.1 => /lib64/librt.so.1 (0x00002b597abb0000) libc.so.6 => /lib64/libc.so.6 (0x00002b597adb8000) libssp.so.0 => /usr/lib64/../lib64/libssp.so.0 (0x00002b597b182000) /lib64/ld-linux-x86-64.so.2 (0x00002b5978f78000)

Hey everyone, as I was updating the tvheadend addon to the new plugin system, I thought I could as well update the binary itself to a recent version. The docs state that for this version the following dependencies are required: libavahi-client3 (>= 0.6.16), libavahi-common3 (>= 0.6.16), libc6 (>= 2.15), libdbus-1-3 (>= 1.0.2), libdvbcsa1 (>= 1.1.0), libssl1.0.0 (>= 1.0.0), liburiparser1 (>= 0.6.0), zlib1g (>= 1:1.1.4) Now, I have zlib-1.2.8-x86_64-1 uriparser-0.7.5-x86_64-1 libiconv-1.13.1-x86_64-2 installed. When I try to start tvheadend I get libssl.so.1.0.0: no version information available (required by tvheadend) libcrypto.so.1.0.0: no version information available (required by tvheadend) I even tried to manually install the latest openssl pack from slackware. Any idea what this could mean; how I could resolve the issue? I very much appreciate your help!

Awesome thanks!

hi mettbrot, please see the OP FAQ section, this should answer your questions, the last update to sickrage was only a day or so ago, so a quick force update should get you to the latest release Hey thanks for the reply. I regularly check the docker page with the update button and install them as they appear. After the latest docker update (and another one using "force update") sickrage still tells me I am on a version from Nov 2014 and 1871 commits behind. thank you for your help. Is anyone else experiencing this? Is there a way to see the version of sickrage currently installed right from the web interface?