| 0 | This is the default value for the flags entry if it is omitted.
If the given old-ini-entry key is present in the INI files, replace that key=value with the given new-ini-entry. Only the keys in the INI files must match. The corresponding value of each such key is ignored.
To add a new-ini-entry to the destination INI file unconditionally, omit the old-ini-entry value from the entry in the update-ini section of the INF.
To delete an old-ini-entry from the destination INI file unconditionally, omit the new-ini-entry value.
If the given old-ini-entry (key=value) exists in the INI files, replace it in the destination INI file that has the given new-ini-entry. Both the key and value of the specified old-ini-entry must match those in the INI files for such a replacement to be made, not just their keys as for the preceding flags value.
If the key that is specified for old-ini-entry cannot be found in the destination INI file, do nothing. Otherwise, the changes made depend on matches found in the INI files for the given keys of old-ini-entry and new-ini-entry, as follows:
If the key of the old-ini-entry exists in the INI files but so does the key of the new-ini-entry, replace the old-ini-entry with the new-ini-entry in the destination INI file and, then, remove the superfluous new-ini-entry from that INI file.
If the key of the old-ini-entry exists in the INI files but the key of the new-ini-entry does not, replace the old-ini-entryВ key with that of the new-ini-entry in the destination INI file but leave the value of the old-ini-entry unchanged.
If the key and value specified for old-ini-entry cannot be found in the INI files, do nothing. Otherwise, the changes made depend on matches found in the INI files for the given keys and values of old-ini-entry and new-ini-entry, as follows:
If the key=value of the old-ini-entry exists in the INI files but so does the key=value of the new-ini-entry, replace the old-ini-entry with the new-ini-entry in the destination INI file and, then, remove the superfluous new-ini-entry from that INI file.
If the key=value of the old-ini-entry exists in the INI files but the new-ini-entry does not, replace the old-ini-entry with the new-ini-entry in the destination INI file but leave the value of the old-ini-entry unchanged.
Remarks
A given update-ini-section name must be unique within the INF file and must follow the general rules for defining section names. For more information about these rules, see General Syntax Rules for INF Files.
The INF provides the full path of the given ini-file on the distribution media in one of the following ways:
Any filename specified within an old-ini-entry or new-ini-entry should designate the destination directory that contains that file. Such a destination directory path of a filename in an update-ini-section entry must be specified as a dirid. For lists of possible dirid values, see Using Dirids.
Источник
Configuration file htaccess
Let’s begin from a far distance with the goal that the novices can see how the file described in the article works. To work the website on the Internet, you need not just a PC and access to the network, yet additionally, extraordinary programming introduced on it, which gives access to information utilizing the HTTP and HTTPS conventions. This product is the web server. There are different sorts of web servers, however, the most widely recognized is Apache. It is based on the open-source code, free, is continually being improved and enhanced, compatible with many scripts, and works on almost all platforms, including Windows, Linux, Netware 5.x.
Apache is arranged by means of design documents that are put away in content organization. With their assistance, you can set explicit standards of activity of the web server. The principle design record is called httpd.conf or apache.conf (contingent upon the OS conveyance). Much of the time, all server setups can be determined here, and essentially this technique is best in light of the fact that:
Table of contents
Mac OS files starting with a dot are invisible. Therefore, you can call it differently and after, transferring via FTP to the hosting, rename it. Usually they place the file in the root directory of the web server (/ public_html) or in the root directory of the site (/public_html/site.com/).
.htaccess syntax
.htaccess opportunities
Access control
Order Deny, Allow
Deny from all
Web access ban, except for IP:
Web access ban for IP:
Directory security with the password:
Working with the web-server errors
Sometimes, instead of the expected page, a visitor may encounter a web server response in the form of an error with a concise, but not always clear for a simple user, explanation of the reason. A complete list of status codes can be found on Wikipedia. For the most common (for example, 404 or 500 errors), it is desirable to create your own page that looks better and presents the exit route to the visitor. It is set as follows:
Adjusting the redirect 301 in htaccess
To create a permanent redirect, the directive 301 redirect is used, which transfers the entire weight of the page to a new url (therefore, it is preferable to a 302 redirect for SEO purposes).
Redirecting the entire site to a new domain:
Redirect page to new:
Mod rewrite redirect module
The mod_rewrite module is an indispensable mechanism for changing URLs “on the fly”. Its utility, and at the same time, the difficulty lies in the fact that you can use a myriad of rules that include even more variables.
For the module to work, first of all we need directives
RewriteEngine On (includes the conversion engine)
Options FollowSymLinks (mod_rewrite operation condition).
If the server administrator has disabled this option for the user directory, then the conversion mechanism cannot be used. This restriction is imposed on virtual hosting servers for security purposes.
For further acquaintance with the module we recommend to refer to the source.
RewriteRule
One of the most functional directives of the mod_rewrite module is the RewriteRule. To specify the condition under which the rule will work, the RewriteCond directive is used. It (one or more) must be prescribed before the RewriteRule.
Redirect page to new domain:
Redirecting a site from a domain without www to a domain from www:
HTTPS redirection (you must first install an HTTPS certificate):
Defining the encoding
The symbol table in which to open the site is determined by the browser. However, you can set the default encoding:
Often the page itself carries in itself (namely in the title) information about the encoding used. It is necessary to check that the specified encoding in the document and in the configuration file matches. The utf-8 given here is almost always required when working with popular cms, since they are designed for a wide range of users around the world. By the way, by default, the same encoding is configured on our shared hosting servers.
Other opportunities
— Determine the site index file:
By default, the index page is considered index.html. With the help of the following directive, you can specify another file name that comes off first when accessing the directory:
— A useful directive is FilesMatch, which specifies the limits of the rule by file name using regular expressions. With its help, for example, you can deny access to certain files:
There are some directives that are not supported on our shared hosting servers, but you can allow them on your VPS, for example.
The reason is that the web server running as suPHP does not support php_flag and php_value. Therefore, we suggest using cPanel (the subsection “Choosing a PHP Version” subsection is extremely useful, to work with error_log — “Error Log”) or to create a local php.ini file for this purpose. We did bring a couple of directives below:
— In order to avoid a web server freeze when processing incorrectly written scripts, there is max_execution_time. With its help, the time in seconds allocated for processing the PHP script is indicated. You can increase the timeout of the web server when executing the script:
— Determine the maximum upload file size:
— Print PHP errors into a separate file:
You can check the file operation by writing simple directives that, with the correct syntax and correct httpd settings (as described at the beginning of the article) should work:
— for example, by denying access to the site from the outside using a directive
— or writing to the file a set of meaningless characters that are not directives. If the web server interacts with htaccess, then, of course, it will not be able to read them and give 500 error.
If the problem really exists, you must first look for the cause in the main configuration file:
— verify that a VirtualHost entry has been created for the domain. As an example:
— the hostname of the server is present (specified when creating URL redirects) as the IP address of the server or domain:
It is highly desirable to make a backup copy of the file before any editing, so that at the worst outcome you can “roll back” the changes back.
We recommend making changes step by step, using a minimum of directives — and in case of failure it will be easier to calculate which rule caused the error.
Useful links
Источник
INI Configuration File
Process Lasso
Using the INI Configuration File
The configuration options and process rules are stored in INI configuration file(s). You can manually edit this INI file, import/export it, choose an alternate INI file to use, or pretend it doesn’t exist. Usually system and network administrators, or those with a lot of process rules need to manually tweak the INI file. Otherwise, the Process Lasso graphical user interface (GUI) will help you edit it. There an option in the File menu to manually open it, if you must. This is discouraged though.
Configuration Profiles
When you create a new ‘config profile’ under the File menu, a new subdirectory and ‘prolasso.ini’ configuration is created. Then you can swap between the configurations. OR you can just use the ‘default’ configuration, which does not mean the default settings, just the un-named root (beginning) configuration file.
Where is the INI configuration file located?
By default, Process Lasso automatically generates a configuration file for each user context in which it runs. These configuration files are located in the “ProcessLasso” subfolder of the respective user’s application data folder. The log is also stored in this same location. The ‘About’ window of Process Lasso will show the full paths.
Administrators can change the path of the configuration file so that all instances of Process Lasso/Process Governor use the same configuration file. This can be done running the installer again and choosing a global configuration path in the second configuration dialog.
Sample Configuration File
#
# prolasso.ini configuration file [sample]
# any line not recognized is ignored
#
[OutOfControlProcessRestraint]
OocOn=True
TotalProcessorUsageBeforeRestraint=85
PerProcessUsageBeforeRestraint=20
TimeOverQuotaBeforeRestraint=2800
PerProcessUsageForRestore=10
PlayOnRestraint=C:\Windows\media\Windows Pop-up Blocked.wav
PlayOnRestore=C:\Windows\media\Windows Feed Discovered.wav
MinimumTimeOfRestraint=6000
TameOnlyNormal=True
LowerToIdleInsteadOfBelowNormal=False
ExcludeServices=False
PlaySoundOnRestraint=False
PlaySoundOnRestore=False
RestrainByAffinity=False
RestraintAffinity=
ExcludeForegroundProcesses=True
DoNotLowerPriorityClass=False
OocExclusions=
[GUI]
HideGraph=False
HideProcessIcons=False
ShowGraphLegend=True
ClearLogAtExit=False
[Performance]
ManageOnlyCurrentUser=True
ExitOnCloseWindow=False
BoostForegroundThread=False
BoostForegroundProcess=False
SoundsOff=True
AggressivelyTrimProcessLassoWorkingSet=True
CloseApplicationTimeoutSeconds=10
ForcedMode=False
[Updates]
CheckForUpdates=False
[SystemTrayIcon]
UseStaticIcon=False
ShowResponsivnessInTrayInsteadOfProcessorUsage=False
[Logging]
LogAllProcessesExecuted=False
LogProcessesDisallowed=True
LogDefaultPriorityAdjustments=True
LogDefaultAffinityAdjustments=True
LogOutOfControlProcessesRestrained=True
LogOutOfControlProcessesRestored=True
LogInstanceLimitTerminations=True
MaximumLogEntries=50
[MemoryManagement]
TrimAllProcessesAtThisIntervalInMs=0
[SysTrayBalloons]
ShowBalloons=False
BalloonTipDuration=10000
ShowBalloonsForOocPriorityRestoration=False
[Performance]
UpdateSpeed=1000
[ProcessAllowances]
AllowedProcesses=badprog2.exe
DisallowedProcesses=badprog*.exe
InstanceLimitedProcesses=word.exe,excel.exe
[ProcessDefaults]
DefaultPriorities=notepad.exe,above normal;calc.exe,above normal
DefaultAffinities=notepad.exe,1;calc.exe,0
MatchWildcardsToPathnames=False
[AdvancedRules]
WatchdogRules=someproc1.exe:billy;0;2;100;2000;0;0;0,someproc2.exe:joe;0;2;100;2000;0;0;0 |
Names encapsulated in ‘[‘ and ‘]’ are groups of options. Each group has one or more options (called keys) that are set to values. Each key is optional, and if it doesn’t exist the default value is used. Lines that do not contain a recognized key or group name are ignored. This file is not case sensitive.
Groups Overview
| Group | Description | Keys |
| Performance | Configures performance related parameters. | UpdateSpeed |
| OutOfControlProcessRestraint | Configures parameters related to restraint of out of control processes (those consuming too many system resources). | OocOn
TotalProcessorUsageBeforeRestaint
PerProcessUsageBeforeRestraint
TimeOverQuotaBeforeRestraint
ProcessUsageQuotaCausingRestore
OocExclusions |
| ProcessAllowances | Configures processes allowed and disallowed from execution. | AllowedProcesses
DisallowedProcesses
InstanceLimitedProcesses
MatchDisallowedWildcardsToPathnames |
| ProcessDefaults | Configures default process priorities. | DefaultPriorities |
| Logging | Configures logging options. | LogAllProcessesExecuted
LogProcessesDisallowed
LogDefaultPriorityAdjustments
LogOutOfControlProcessesRestrained
LogInstanceLimitTerminations
MaximumLogEntries |
| AdvancedRules | Sets more advanced process rules. | WatchdogActions |
Defined keys (options) and their accepted values are as follows:
| Group | Key | Description | Accepted Values and Format | Default Value |
| Performance | UpdateSpeed | The interval between enumerations of running processes by ProcessGovernor and ProcessLasso, in milliseconds. The lower the interval more responsive the applications are to changes in running processes, but more CPU cycles are used. | Any non-negative number. It is not recommended to exceed 4000ms or go below 500ms. It is recommended to keep this value the default. | 1500 |
| Performance | ForcedMode | When forced mode is enabled, Process Lasso more aggressively enforces default priorities and affinities. Some applications change their own priorities, and this setting may be necessary in such cases. | ‘True’ if this feature is enabled, ‘False’ if not. | False |
| OutOfControlProcessRestraint | OocOn | Toggles out-of-control process restraint on or off. | ‘True’ if this feature is enabled, ‘False’ if not. | True |
| OutOfControlProcessRestraint | TotalProcessorUsageBeforeRestraint | The percentage of processor(s) in use that initiates a check of processes that may be out-of-control. While the total processor usage is below this threshold, processes are not restrained. This value includes usage of all processors on a system. | Range: 1-100. | 75 |
| OutOfControlProcessRestraint | TimeOverQuotaBeforeRestraint | Number of milliseconds above ProcessorUsageQuota before the process priority is lowered. | Any non-negative number. | 1750 |
| OutOfControlProcessRestraint | PerProcessUsageQuotaBeforeRestraint | The percentage of processor(s) in use by a process before its priority is reduced. Note that TotalProcessorUsageBeforeRestraint must have already been met. | 1-100. This value must be equal to or lesser than ProcessorUsageQuota. | 20 |
| OutOfControlProcessRestraint | PerProcessUsageQuotaForRestore | The percentage of processor(s) in use by a process that is considered a safe enough value to restore a preciously restrained process to its original priority. | 1-100. This value must be equal to or lesser than ProcessorUsageQuota. | 5 |
| OutOfControlProcessRestraint | OocExclusions | Processes excluded from out-of-control restraint. | This is a comma delimitered list of process names. Wildcards are allowed.
Format:
process1,process2,process3
Example:
taskmgr.exe, game*.exe | None. |
| AdvancedRules | WatchdogRules | Complex watchdog operations. | See below. | n/a |
| ProcessAllowances | DisallowedProcesses | Processes disallowed to execute. If a process is launched matching a specification in this list, it will be terminated. | This is a comma delimitered list of process names. Wildcards are allowed.
Format:
process1,process2,process3
Example:
taskmgr.exe, game*.exe |
| ProcessAllowances | AllowedProcesses | Processes allowed to execute. These are only applicable if they match a process specification in the DisallowedProcesses key. For example, if notepad*.exe is lised in DisallowedProcesses and notepad1.exe is listed in AllowedProcesses, then notepad1.exe will be allowed to execute, but notrpad2.exe will not. | This is a comma delimitered list of process names. Wildcards are allowed.
Format:
process1,process2,process3
Example:
taskmgr.exe, game*.exe | None. |
| ProcessAllowances | InstanceLimitedProcesses | This variables provides a list of processes who should be limited to no more than a certain number of instances in a given user session. | This is a comma delimitered list of process names, with semicolons used to indicate the maximum instance count.
Example:
myprogram.exe;2 |
| ProcessDefaults | DefaultPriorities | A list of default priorities for processes. | This is a comma delimitered list of process names and priorities. Wildcards are allowed. Valid priorities are: Format:
process1,priority1,process2,priority2
Example:
taskmgr.exe, high,*.scr,idle | None. |
| Logging | LogAllProcessesExecuted | Toggle logging of all processes executed. | ‘True’ if enabled, ‘False’ if not. | False |
| Logging | LogProcessesDisallowed | Toggle logging of processes terminated because they were disallowed. | ‘True’ if enabled, ‘False’ if not. | True |
| Logging | LogDefaultPriorityAdjustments | Toggle logging of processes whose priority was adjusted to a configured default value. | ‘True’ if enabled, ‘False’ if not. | True |
| Logging | LogOutOfControlProcesses | Toggle logging of processes restrained because they were found to be out-of-control. | ‘True’ if enabled, ‘False’ if not. | True |
| Logging | MaximumLogEntries | The maximum number of log entries. When the log file reaches this limit, it is resized to 80% of this value. | Minimum reasonable value is 10. | 500 |
| Logging | LogInstanceLimitTerminations | Set to log terminations of processes based on their instance limit, as configured. | ‘True’ if enabled, ‘False’ if not | True |
Peformance note: Process Lasso uses its own high performance INI parsing algorithm.
Documentation of WatchdogRules
| Field 1 | Field 2 | Field 3 | Field 4 | Field 5 | Field 6 | Field 7 | Field 8 |
|---|
| Process PL ‘actualized’ base name and user | Action Type | Metric In Question | Threshold | Duration | Action Specific Value | Type Specific Value | Compare Type |
Field 1: Process PL ‘actualized’ base name and user
This field accepts the base name for which you want the rule to match. It is actualized into the format that you see Process Lasso display in its GUI. That means that service names and/or service group names may also be included in the base name. The username may also be specified by using a colon as a delimter. Both accept wildcards. Examples, “myprocess*.exe:MyUser” – “myprocess*:My*”.
Field 2: Action Type
Field 3: Metric In Question
Field 4: Threshold
This is the threshold for action. If Field 3 is CPU, then this is % of total CPU used of time. If Field 3 is Memory (1), then this is MEGABYTES.
Field 5: Duration
This is the length of time the process remains over threshold before the watchdog action is triggered, stored in milliseconds.
Field 6: Action Type Specific
This can be any number of values depending on the Action Type
If set to change CPU priorities
Field 7: Type Specific Value
When a CPU metric we are looking at:
Field 8: Comparison Type
Источник