Jump to content

Squid

Community Developer
  • Posts

    28,769
  • Joined

  • Last visited

  • Days Won

    314

Everything posted by Squid

  1. Truth be told, there was no reason to even issue an update since there was nothing actually wrong. I messed up originally be redoing the txz so pretty much had to update to 11a...
  2. Part of my workflow. On days with multiple versions, the day's original version winds up getting deleted from GitHub
  3. Suppressed. I tested the snot out of upgrading to the new version which wouldn't have displayed that line, but didn't check the console after a reboot or clean install You're good for keeping me on my toes
  4. Does this fix the problem with AutoUpdate not working also? http://lime-technology.com/forum/index.php?topic=40262.msg513917#msg513917 Yes Sent from my LG-D852 using Tapatalk
  5. I had that fixed. [emoji20] must have messed up the plg versions in testing Sent from my LG-D852 using Tapatalk
  6. https://upload.wikimedia.org/wikipedia/en/7/79/Vimy_Memorial_(September_2010)_cropped.jpg[/img] - Separated out, CA Appdata Backup/Restore, Plugin Autoupdate, and Cleanup Appdata After installing this update (and on all new installs of CA), those 3 plugins will automatically be installed (for those users already utilizing those modules), and the settings migrated over to the new plugins (Plugin Auto Update Cleanup Appdata Appdata Backup / Restore) If you choose to, those modules can be separately uninstalled either via the Plugins tab, or via CA's Installed Apps section These changes should simplify my work flow any future bug fixes, etc. Future planned modules for CA will be a 100% separate download Other Changes - The manual for CA (and the other plugins) is now downloaded separately on demand
  7. A plugin designed to scan your docker appdata share for folders that are no longer used by Docker applications and prompt you if you would like them deleted. Formerly part of Community Applications, this module is now packaged separately. This plugin will automatically be installed with new installs of CA, but is now able to be uninstalled separately from CA, or installed separately (if CA is not installed) To install this plugin separately, either go to CA's CA Modules section and install it from there. If for some reason, you do not have CA installed on your system, then paste the following url into the Install Plugins section: https://raw.githubusercontent.com/Squidly271/ca.cleanup.appdata/master/plugins/ca.cleanup.appdata.plg Note: This plugin is deprecated. While it is 100% fully functional, I got tired of being blamed every time somebody massively misconfigured an app, then ran the plugin and answered all the questions without even thinking for a second.
  8. A plugin designed to manually or on a schedule create backups of your Docker appdata (and Flash Drive and VM XML's) Formerly part of Community Applications, this module is now packaged separately. This plugin will automatically be installed with new installs of CA, but is now able to be uninstalled separately from CA, or installed separately (if CA is not installed)
  9. A plugin designed to keep all (or selected) plugins / dockers up to date, with options for delayed upgrades. Formerly part of Community Applications, this module is now packaged separately. To install this plugin, go to the Apps Tab and search for Auto Update. Note that if you are utilizing CA's Appdata Backup / Restore module, then with this module installed you can also tell the Backup procedure to update the docker apps at the same time as the backup occurs
  10. Settings - Docker - Advanced Stop the docker service, then delete the image Then re-add the apps via CA's Previous Apps section (or the old school way of Docker - Add Container - Select the my* template via the template drop down) http://lime-technology.com/forum/index.php?topic=40937.msg481138#msg481138
  11. LT like to keep you on your toes don't they.... Just discovered the other day that within CA clicking on a running container's icon within the resource monitor or the more info link on the full description wouldn't take you to cAdvisor, due to a change somewhere in 6.3...
  12. That's what I said. Where? Sent from my LG-D852 using Tapatalk Here.... Yeah well I guess I can be forgiven since it was a cross post Sent from my LG-D852 using Tapatalk
  13. That's what I said. Where? Sent from my LG-D852 using Tapatalk
  14. It means your docker.img file is full. Check out the docker FAQ for lots of reasons why Sent from my LG-D852 using Tapatalk
  15. I thought Bonienl reverted those changes. Sent from my LG-D852 using Tapatalk If he did, I missed the memo on that. Mobile so pita for me to find the post but IIRC he changed it, then my plugins would wind up crashing so he reverted them Sent from my LG-D852 using Tapatalk
  16. I thought Bonienl reverted those changes. Sent from my LG-D852 using Tapatalk
  17. Wondered why I kept getting all the log files. I don't see anything re Troubleshooting Mode in FCP Settings. How do I disable it? By design the only way is a reboot Sent from my SM-T560NU using Tapatalk
  18. Is there a reason you're running FCP's troubleshooting mode? Just curious But the auto update thing I had already saw the issue before you posted... I'm just in the middle of other updates to CA that aren't fully tested as of yet, so it'll be a day or two... (already fixed on my development routine)
  19. You'd have to post the diagnostics / syslog (CA logs the autoupdate runs)
  20. Your docker.img file is completely trashed, and needs to be deleted and recreated. Unfortunately, the syslog doesn't go back to where ransomware tripped, so I can't tell you why it did a "double trip" and over wrote the backup of the share.cfg files (which is why restoring normal access is doing nothing). If might be helpful if you post the contents of boot/config/plugins/ransomware.bait/smbStatusFile.txt which will at least let me see the times that the system tripped. I have been looking at handling the backups of the normal share settings a little different. As to the solution, because the backup files don't exist, you've got to reset the user permissions on those shares to what they should be. FCP was definitely failing on writing to the cache drive, and complaining that the cacheFloor setting is less that the free space available. But the docker problem, and the cache would be separate issues from RP
  21. Ah... So your going to begin Beta testing the backup now? Only 6 months late
  22. Only when passing through a GPU, but yes, this should be noted. Also add that ballooning is not available whenever you pass through a PCI device to a virtual machine. Those VMs will always fully allocate the max amount of memory assigned. As the LT expert, hop to it. ? Sent from my LG-D852 using Tapatalk
  23. Never really paid any attention to the load average, but if you've got an issue with other apps being held up because of this, you should read this FAQ entry http://lime-technology.com/forum/index.php?topic=40937.msg492111#msg492111
×
×
  • Create New...