Ansible
PS DSC
Downloads:
23,460
Downloads of v 9.0.0.456:
20,291
Last Update:
12 Jul 2018
Package Maintainer(s):
Software Author(s):
- Jeremy Collake
Tags:
prioritize process manager execute priority optimizer admin
Process Lasso
- 1
- 2
- 3
9.0.0.456 | Updated: 12 Jul 2018
Downloads:
23,460
Downloads of v 9.0.0.456:
20,291
Maintainer(s):
Software Author(s):
- Jeremy Collake
Process Lasso 9.0.0.456
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Jeremy Collake. The inclusion of Jeremy Collake trademark(s), if any, upon this webpage is solely to identify Jeremy Collake goods or services and not for commercial purposes.
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
Validation Testing Passed
Verification Testing Failed
DetailsScan Testing Resulted in Flagged:
This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.
We recommend clicking the "Details" link to make your own decision on installing this package.
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Process Lasso, run the following command from the command line or from PowerShell:
To upgrade Process Lasso, run the following command from the command line or from PowerShell:
To uninstall Process Lasso, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download plasso --internalize --source=https://community.chocolatey.org/api/v2/ -
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'" - Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade plasso -y --source="'INTERNAL REPO URL'" [other options]See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade plasso -y --source="'INTERNAL REPO URL'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install plasso
win_chocolatey:
name: plasso
version: '9.0.0.456'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'plasso' do
action :install
source 'INTERNAL REPO URL'
version '9.0.0.456'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller plasso
{
Name = "plasso"
Version = "9.0.0.456"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'plasso':
ensure => '9.0.0.456',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was approved as a trusted package on 12 Jul 2018.
Process Lasso is a tool designed to manage and edit how your processes and services run.
It offers a robust list of capabilities including default process priorities and affinities, termination of disallowed processes, instance count limits, a system responsiveness graph, logging of processes, keep select processes running (auto-restart), and much more.
Features
- ProBalance dynamic priority optimization
- Persistent (sticky) priorities and CPU affinities
- Instance count limits
- Disallowed processes
- Keep processes running (auto-restart)
- Unique system responsiveness graph
- Prevent PC sleep for designated processes
- Differentiate between svchost.exe instances
- Extremely low resource use
- Stand-alone process management engine (uses as little as 1MB of RAM)
- Event logging
Package parameters
To pass parameters, use --params "''" (e.g. choco install packageID [other options] --params="'/ITEM:value /ITEM2:value2 /FLAG_BOOLEAN'").
To have choco remember parameters on upgrade, be sure to set choco feature enable -n=useRememberedArgumentsForUpgrades.
/language:- This indicates the language to use. - defaults to "English"/gui_start_type:- This indicates whether to start the GUI at login for ALL users (all), for only the current user (current), or neither (manual). The current user is the user context in which the installer is running. - defaults to "all,uac"/governor_start_type:- This indicates whether to start the core engine (processgovernor) at login for ALL users (all), for only the current user (current), or neither (manual). The current user is the user context in which the installer is running. - defaults to "all,uac"/launch_gui- This indicates whether or not to launch the GUI after installation. Even when the GUI is launched, it remains minimized to the system tray. - if not passed defaults to "false"/logfolder:- This indicates to use a global log folder for ALL users on the system. By default, each user has his or her own log folder in their respective application data directory. However, it is sometimes desirable to consolidate all log events into a single log folder. Be sure that this log folder is writable by all users on the system. - defaults to "%appdata%\ProcessLasso\logs"/configfolder:- This indicates to use a global configuration folder for ALL users on the system. By default, each user has his or her own configuration in their respective application data directory. However,it is sometimes desirable to use the same configuration for all users, and is required when the governor is run as a service. Be sure that this configuration folder is at least readable by all users, and writable by those who you wish to allow configuration changes. - defaults to "%appdata%\ProcessLasso\config"
Notes
This will always install the latest version of Process Lasso, regardless of the version specified in the package.
When using a user-defined config and log path, we recommend storing the config in a sub-folder, e.g. “C:\ProcessLasso\Config” and the logs in another sub-folder “C:\ProcessLasso\Logs”. The reason we suggest this is because, otherwise, every time the log is written to, it will trigger a file system change notification event on that folder and cause the configuration file to be checked to see if it changed. It won’t be reloaded, so not much overhead, but a little. The granularity of file system change notifications in Windows is limited to folders, thus putting the config in it’s own folder makes sure that only writes to it cause a change notification event.
There is an option for
/governor_start_type:option as a service, but at the current time this package does not support the option to start the governor as a service.
$ErrorActionPreference = 'Stop'
$packageName = 'plasso'
$programUninstallEntryName = 'Process Lasso*'
$registry = Get-UninstallRegistryKey -SoftwareName $programUninstallEntryName
$file = $registry.UninstallString
$packageArgs = @{
packageName = $packageName
fileType = 'exe'
silentArgs = '/S'
validExitCodes = @(0)
file = $file
}
Uninstall-ChocolateyPackage @packageArgs
Log in or click on link to see number of positives.
- plasso.9.0.0.456.nupkg (8bf0cac8b58d) - ## / 60
- processlassosetup64.exe (438b46e653c8) - ## / 68
- processlassosetup32.exe (e2a91427d331) - ## / 66
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
| Add to Builder | Version | Downloads | Last Updated | Status |
|---|---|---|---|---|
| Process Lasso 9.0.0.456 | 20291 | Thursday, July 12, 2018 | Approved | |
| Process Lasso 9.0.0.452 | 455 | Friday, May 4, 2018 | Approved | |
| Process Lasso 9.0.0.442 | 390 | Thursday, March 29, 2018 | Approved | |
| Process Lasso 9.0.0.440 | 387 | Tuesday, March 13, 2018 | Approved | |
| Process Lasso 9.0.0.426 | 420 | Tuesday, January 9, 2018 | Approved | |
| Process Lasso 9.0.0.420 | 357 | Friday, December 8, 2017 | Approved | |
| Process Lasso 9.0.0.402 | 423 | Thursday, September 7, 2017 | Approved | |
| Process Lasso 9.0.0.398 | 369 | Saturday, September 2, 2017 | Approved | |
| Process Lasso 9.0.0.394 | 368 | Monday, August 21, 2017 | Approved |
Bitsum LLC © 2002-2018 - All Rights Reserved Worldwide
-
- chocolatey (≥ 0.10.8)
- chocolatey-core.extension (≥ 1.3.3)
Ground Rules:
- This discussion is only about Process Lasso and the Process Lasso package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Process Lasso, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.