Squid
-
Posts
28,770 -
Joined
-
Last visited
-
Days Won
314
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by Squid
-
This is fixed last night. Reinstalling using default values from the Installed Section will now give the popup.
-
If there's no parity check happening, then something in my detection went wrong somewhere. Just acknowledge the error.
-
No changes to installed applications required.
-
This conversation didn't go quite the way I expected [emoji20] Sent from my LG-D852 using Tapatalk
-
It's called multitasking. Sent from my LG-D852 using Tapatalk
-
http://corntab.com or search for cron on wikipedia . or hover over the what is cron link on the bottom left Sent from my LG-D852 using Tapatalk
-
(SOLVED) modified Plex Docker Config and it Disappeared. I need PLEX!
Squid replied to bedpan's topic in General Support
From the Apps tab, go to Previously installed, reinstall Plex, and fix the parameter. -
Assuming you're running the autovmbackup scripts. That, (and any script) run through User Scripts can be scheduled via the Schedule setting next to the script.
-
I'm dedicated. Teamviewer on my phone in the washroom
-
And inadvertently you found a bug. Figured I'd test what I said, and a reinstall using default values from installed apps did not give the pop up. Fix tonight
-
New installs or reinstalls using default values will give the pop up to select branch. Edits of existing installs will not.
-
You should run a Memtest from the boot menu if only to rule it out.
-
Shouldn't make any difference. But, you have to bear in mind that all paths anywhere in a script should be absolute, and not relative. That, and IIRC (would have to double check after work), but the scripts have slightly different /tmp folders that they execute from depending upon how its started.
-
Explain... Admittedly I have never checked what user a cron entry runs as though Sent from my LG-D852 using Tapatalk
-
Everything should run as root Sent from my LG-D852 using Tapatalk
-
@CHBMB is going to echo the same thing here: Don't ever, ever, ever do that. If you have Fix Common Problems plugin installed, in the same tools tab there is a "Docker Safe New Permissions Tool" that you should run instead if you ever feel that the permissions on the array are messed up for one reason or another.
-
did you rescan?
-
Since you were the first to use that particular term, allow me to state in non PC terms what I think is happening: I have no f*cking clue. The IT guys at my company have no f*cking clue either.
-
Not going to be what you want to hear, but what you wound up proving is that this issue that affects a handful of users is out of my control... And, in the process you also proved that my slight revamp for a possible fix to a problem I can't replicate won't work since the rm command locked up via a direct SSH connection. To be expected. The only thing that I can suggest is to keep plugging away at deleting the old backup sets, then switch to not using backup sets at all. Then the rm commands are never issued ever.
-
/data has to be mapped exactly the same as it is on the download client. See the docker FAQ for ...aka linking containers. Sent from my LG-D852 using Tapatalk
-
Biggies to avoid would be < > &
-
https://forums.lime-technology.com/topic/46802-faq-for-unraid-v6/?page=2#comment-545988
-
I'll save you the time. I posted thinking you were on the lsio flavour. On Binhex's libmediainfo is there, but the mediainfo command is not.
-
docker exec -it radarr /bin/bash followed by mediainfo --Output=HTML /path/to/your/file.mkv Will out the results to the screen. To save it to a file, add to the end of the command > /path/To/WhereToSave/output.html Note that all paths are based on the container path you've specified within the template, not unRaid's normal paths.
-
It means that some of the files within that share are currently sitting on the cache drive. Common and easy way for that to happen is to have the share being written to while use cache disk was set to only, yes, or prefer. And the subsequently switching the share to use cache no, but before mover ran. The fix is to change the setting to be use cache disk yes, run mover from the main tab, then switch it back. If there were no errors (ie: no files were in use), then it should now be fully protected.
