DasMarx

Hi @Pirat and thank you very much for the contribution of this tool. I was testing out the Buddy Backup on Unraid 7.2.2 and hit quite a big road-block. The current location on this os for zfs is in /usr/sbin/zfs which is not present in the PATH of the buddybackup user. root@backup:~# which zfs /usr/sbin/zfs root@backup:~# env | grep PATH PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin And via SSH for that user buddybackup@backup:/home/buddybackup$ env | grep PATH PATH=/usr/local/bin:/usr/bin:/bin I am not sure if zfs was present in older versions for all users, but you can still just call it from the buddybackup user. buddybackup@backup:/home/buddybackup$ /usr/sbin/zfs list NAME USED AVAIL REFER MOUNTPOINT cache 29.8G 869G 128K /mnt/cache I'd appreciate your input if the path was different in the past or if e.g. the user had a different path. I saw that root@backup:~# cat /etc/profile ... # Set the default system $PATH: PATH="/usr/local/bin:/usr/bin:/bin" # For root users, ensure that /usr/local/sbin, /usr/sbin, and /sbin are in # the $PATH. Some means of connection don't add these by default (sshd comes # to mind). if [ id -u" = "0" ]; then echo $PATH | grep /usr/local/sbin 1> /dev/null 2> /dev/null if [ ! $? = 0 ]; then PATH=/usr/local/sbin:/usr/sbin:/sbin:$PATH fi fi Which would explain why we don't have that path as a non-root user.

I tried this on 6.12.0rc5 and it works great to some regards. The idle consumption went from 100% to 20% on my windows vm. However I am not able to open the VM page anymore. I can still the see VMs in the Dasboard and stop/start it but I can't change the VM anymore when clicking on edit as no XML selection is loaded. Is there any other way to change the xml of my VM once it is in this broken state? This may also be a bug in 6.12.0rc5.

I am having some problems lately when a mount goes offline that appdata backup and restore is set to backup too. Using unassinged devices to mount an smb share at /mnt/disks/myshare/ Using this as a target for appdata backup and restore. If, for any reason, that mount goes offline, backup will now fill up my ram inside the /mnt/disks/myshare/ folder. Is there a way to precheck if the remote share is correctly mounted and throwing an error instead of filling up a folder in ram?

But this also means spotify support on my airplay speakers won't work anymore through forked-daapd. For me this is a complete removal of spotify on forked-daapd Will it be added back in a later version?

Hi sparklyballs, I was looking at the changes that have been done recently and would like to question the current changelog: Rebase to alpine linux, remove redundant spotify support, move to main repository This indicates, that spotify is still supported in some way, but it does not show up at any given time? Am i missing some configuration or is this only temporary? https://github.com/linuxserver/docker-daapd/commit/6afec6a0302190f8ee17c274f01e2f4f81d185a6 This commit seem to have removed all parts of the spotify component.

It is actually caused by the fact that mediainfo must be installed inside the docker container. http://www.tinymediamanager.org/index.php/changelog/ 22.01.2016 – Version 2.7.2 ======================= LINUX: We’ve removed the shipped mediainfo library due to massive problems between different distributions. Please install the libmediainfo directly from your package manager or from https://mediaarea.net/ Looking forward to your update hurricanehrndz. Thanks for the great work so far.

@SlrG locale -a C POSIX en_US.utf8 Will change that, but it still does work, nevertheless. Regarding the order, im not sure, but could test if it does make a difference. Ive added the syslog but do not see the actual message that was present in the update there. The update was started at Dec 9 07:28:30, but the proftdp was still on version "ProFTPD 1.3.5". At Dec 9 08:03:21, i reinstalled the plugin and the version went to ProFTPD 1.3.6rc1 syslog.txt

@SlrG the update failed and i could not use the newer version. By failed update, i only mean the proftpd files themself and not the plugin as a whole. I had to save my configuration, uninstal the plugin and reinstall it again but now UTF-8 is announced in the FEAT request: Befehl: FEAT Antwort: 211-Features: Antwort: TVFS Antwort: MFMT Antwort: SIZE Antwort: MFF modify;UNIX.group;UNIX.mode; Antwort: REST STREAM Antwort: MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.mode*;UNIX.owner*; Antwort: UTF8 Antwort: LANG en-US* Antwort: EPRT Antwort: EPSV Antwort: HOST Antwort: MDTM Antwort: 211 End Thanks for your help so far. Additional information for anyone interested what i set inside my proftdp.conf: LangDefault de_DE UseEncoding on LangEngine on

Hello, i have problems accessing files that contain umlauts like ß via ftp. üöä are ok but are not shown correctly. It looks like the version you do offer does not contain the mod_lang module. Are there tips regarding this or do i need an updated of the plugin? Additional information: Using Filezilla to access fails. Using e.g. Chrome does succeed and the files and folders are shown correctly and are accessable. Felix

Hi, unifi has been released in version 4.7.5, will you update your docker? http://community.ubnt.com/t5/UniFi-Updates-Blog/UniFi-4-7-5-is-released/ba-p/1357245