Rumpus 8.0.5 includes additional checks in it's client-side javascripts to help avoid this condition. If that were to happen, Rumpus may detect those requests as possible hack attempts, causing the client to be black-listed due to some temporary file transfer problem. In some cases, if a client session is unexpectedly terminated but a progress indicator remains open, those progress indicator update requests may not be matched to an ongoing session. As users transfer files, Rumpus displays the progress indicator, which requires an update every second to stay current. The first possibility is the file transfer progress indication bar. But I do have two theories on why this is happening. It's a tricky problem, because it's not something I've been able to consistently reproduce in a test environment. I've had more and more reports of perfectly legitimate clients being added to the "Blocked Clients" list in Rumpus. These changes improve compatibility with several different SFTP clients, so if you have enabled SFTP, or ever plan to, be sure you are running Rumpus 8.0.5 or later. Rumpus 8.0.5 includes a few subtle but important changes to it's new SFTP engine. ![]() The "None" option is only there for administrators who know they will never use aliases to grant Rumpus users access to different content folders. So, if you use aliases, which are very handy and are a great feature of the system, by all means, keep using them. With all that said, I freely admit that I'm probably obsessing about an efficiency that will have little or no impact on performance in the real world. The benefit is improved performance in the form of fewer disk accesses and significantly reduced logic when converting Internet URLs into local file system paths. This option disables all aliases for all users accessing the server through Rumpus. ![]() So, while I was implementing the multi-alias-resolution feature anyway, I added the "None" option. ![]() The mere fact that aliases exist slows your server down, whether or not you actually use them. In other words, Rumpus pays a performance penalty resolving aliases, even when the requested file path doesn't include aliases. The problem is that for every requested URL, Rumpus has to check every component of the path to see if it's an alias. "Modern" resolution causes Rumpus to use the new alias APIs, so it's Yosemite-compatible and is the recommended option for servers running OS X 10.10 and later. "Classic" alias resolution works fine on servers running OS X 10.6 through 10.9, and that's the recommended setting for those systems. In Rumpus 8.0.5, if you open the Network Settings window, flip to the Preferences tab, and open the Advanced Preferences sheet, you now have the option to use "Classic" alias resolution or "Modern". ![]() Granted, modern Macs are so fast it may not matter much, but I obsess over efficiency and performance, so Rumpus continued to use the older APIs, even though they weren't recommended by Apple. I had looked at moving to the newer alias APIs a couple of years ago, but in testing found them to be about 50% slower than the older APIs. The Rumpus 8.0.5 update implements Apple's latest alias resolution APIs to solve this problem. Basically, if you create an alias on a Mac running OS X 10.10, and the server is running Rumpus 8.0.4 or earlier, Rumpus users simply won't see it. The complete list of updates is included below, but there are a couple of items that bear special attention.ĭownload The Latest Release Of Rumpus HereĪ change in Yosemite (OS X 10.10) caused Mac OS aliases created under Yosemite to fail in Rumpus. You can get more information by clicking the links to visit the relevant pages on the vendors website.I don't usually write blog posts for maintenance updates, but Rumpus 8.0.5 has some pretty significant changes, and it's a highly recommended upgrade for all Rumpus for Mac servers. The links provided point to pages on the vendors websites. The information is provided "As Is" without warranty of any kind. Update for FileZilla Client For Mac (3.34.0)Īffected Product Information Product Nameĭisclaimer: This webpage is intended to provide you information about patch announcement for certain specific software products.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |