Jump to content

perrin

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About perrin

  • Rank
    Newbie

Converted

  • Gender
    Undisclosed
  1. I also had this issue in 5.0b14. I just upgraded to 5.0RC1 and am now able to mount a smb share without any issue.
  2. Is there a recommended way of testing for the array being online? Some of my addons access the cache drive, and I have a little script which I use to wait for the cache drive coming ready: I am using the emhttp events to start items that require the array be online when they start. If you look at /boot/custom/emhttp_event/event, there are sections for different array 'states' case $1 in disks_mounted) /boot/packages/twonkymedia-i386-glibc-2.2.5-6.0.38.sh ;; svcs_restarted) if ! ps -ef|grep twonkymedia|grep -v grep; then cd /usr/local/twonkymedia/ /usr/local/twonkymedia/twonkymedia.sh start fi ;; unmounting_disks) if ps -ef|grep twonkymedia|grep -v grep; then /usr/local/twonkymedia/twonkymedia.sh stop fi ;; *) logger -t Event\ Script Incorrect\ Argument ;; esac HTH Rob
  3. I have mine installed to /mnt/cache/.custom and update using their web interfaces without any issues.
  4. ahh make sense, I need to figure out how to run it as nobody then because I use the auto processing. If you don't get the apps running as nobody, this should work for you. This requires you install the inotify tools (can be installed from unmenu package manager) #!/bin/sh inotifywait -m -r --event close_write --event moved_to /mnt/user/TV/ --format "newperms \"%w\" " | sh this command says wait until the file is completely written (ie. act on finish, not start of copy/move) in the TV user share and then run the newperms commands on everything in the TV folder; this might be a bit disk intensive (and will spinup drives). You can set the path to whichever user share you are saving the downloads in. Just save this to a file and start it from the go script -- i use echo "/boot/config/watch_tv.sh" | at now +1 minute so it launches in the background.
  5. Sab + Sickbeard are running as root by default, so all the files they create are owned by root.root, not nobody.user which makes them inaccessible via user shares. I have a added the unraid newperms command to the post-processing scripts i use (I don't use the Sickbeard auto-process ones) and it seems to work well. Here is the line to add to your script (you can also make a script that only does the one thing): /usr/local/sbin/newperms "$1"