• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Rogue perl process

Yes, it works and stops other stuff, but it didnt stop those. Those all returned a success status to the client.

Also ASL in scan mode, and from GUI detected no problems with mod sec to boot during this time.
 
Yep, we've got a lot of new toys in the B3 release. I think you saw some of the iframe stuff that we started in B2. The basics are in asl-2.0-testing now, but you really need the B3 framework to take advantage of it. Knock on wood I should get that into -bleeding today or tomorrow.
 
Which one should be used for production server, and which one for testing? I ask becuase I think I remember you saying that the testing was the stable branch at one point, but cant remember how your branches worked.
 
This applies for both atomic and ASL

atomic / asl-2.0 - stable production code
atomic-testing / asl-2.0 - QA release, these contain known problems, or fixes to known problems, but aren't yet production quality
atomic-bleeding / asl-2.0-bleeding - untested, or direct builds from subversion. Unknown problems, unknown quality

ATrpms follows the same model, and I think some other archives (livna? dries?) might as well. I stole that layout from axel thimm.
 
Back
Top