proftpd - MaxStoreFileSize
2 отговора
39 прегледа
Re: proftpd - MaxStoreFileSize
тази директива май я има само от 1.2.7 нагоре
но аз междувременно намерих обяснение на едно единствено място в целия интернет - не знам защо не са го включили в userguide:
-----------------------------------------------------------------------------
TJ Saunders <[email protected]>
2001-10-29
-------------------------------------------------------------------------
Problem
------------------------------------------------------------------------
Many FTP administrators would like to be able to place size limits on
any single file that a client might upload. Others, though less common,
would like to place similar size restrictions on the size of files
downloaded from their servers.
----------------------------------------------------------------------------
Solution
----------------------------------------------------------------------------
Create two new configuration directives, MaxRetrieveFileSize (for
download restrictions) and MaxStoreFileSize (for upload restrictions).
Syntax: MaxRetrieveFileSize number|"*" units ["user"|"group"|"class" expression]
Default: Unlimited
Context: server config, <VirtualHost>, <Anonymous>, <Global>,
<Directory>, .ftpaccess
Module: mod_xfer
Compatibility: 1.2.4 and later
When downloading files to clients (eg serving a RETR request), the
server will check for any configured limit against the size of the file
being requested, and abort any transfers if the requested file's size
exceeds the configured limit.
A single "*" argument configures unlimited file sizes, and is used
primarily to override any inherited restrictions from higher contexts.
The given number is the number of bytes for the limit, and is followed
by a units specifier of (case-insensitive) "Gb" (Gigabytes),
"Mb" (Megabytes), "Kb" (Kilobytes), or "B" (bytes). The given number of
bytes is multiplied by the appropriate factor.
The optional parameters are used to restrict the file size limits only
to specific users. If the "user" restriction is given, then expression is a
user-expression specifying to which users the rule applies. Similarly for the
"group" restriction. For the "class" restriction, the expression is simply
the name of connection class for whom the rule will apply. If no matching
user, group, or class expression is found for the current user (in that
order), then a limit with no expression (ie no "user", "group", or "class"
identifier) is applied.
Examples:
# restrict downloads to only 1 gigabyte
MaxRetrieveFileSize 1 Gb
# restrict downloads for user fred, but allow unlimited download size for
# everyone else
MaxStoreFileSize 50 Kb user fred
MaxStoreFileSize *
See Also: MaxStoreFileSize
-----------------------------------------------
Syntax: MaxStoreFileSize number|"*" units ["user"|"group"|"class" expression]
Default: Unlimited
Context: server config, <VirtualHost>, <Anonymous>, <Global>,
<Directory>, .ftpaccess
Module: mod_xfer
Compatibility: 1.2.4 and later
When uploading files from a client (eg serving a STOR request), the
server will check for any configured limit against the size of the file
being sent, and abort any transfers if/when the given file's size
exceeds the configured limit.
A single "*" argument configures unlimited file sizes, and is used
primarily to override any inherited restrictions from higher contexts.
The given number is the number of bytes for the limit, and is followed
by a units specifier of (case-insensitive) "Gb" (Gigabytes),
"Mb" (Megabytes), "Kb" (Kilobytes), or "B" (bytes). The given number of
bytes is multiplied by the appropriate factor.
The optional parameters are used to restrict the file size limits only
to specific users. If the "user" restriction is given, then expression is a
user-expression specifying to which users the rule applies. Similarly for the
"group" restriction. For the "class" restriction, the expression is simply
the name of connection class for whom the rule will apply. If no matching
user, group, or class expression is found for the current user (in that
order), then a limit with no expression (ie no "user", "group", or "class"
identifier) is applied.
Examples:
# restrict upload to only 3 megabytes
MaxStoreFileSize 3 Mb
# restrict anonymous uploads to 50k, but allow unlimited upload size for
# everyone else
MaxStoreFileSize 50 Kb user anonymous
MaxStoreFileSize *
See Also: MaxRetrieveFileSize
----------------------------------------------------------------------------
Comments
----------------------------------------------------------------------------
Patch updated as of 2001-10-29 (1.2.4 release). Note that the directive
syntax has changed slightly (units specifier is now separate from the
number, and is a required argument).
Patch updated as of 2001-03-01 (1.2.1 release)
If/when this patch is accepted into the official source tree, or there
is a large user demand, I'll generate documentation patches.
Patch updated to work correctly on FreeBSD platforms, which had trouble
with the SIZE_MAX macro. Thanks to Vladimir Kotal <[email protected]>
for the bug report and fix.
2001-03-29: updated for recent proftpd-1.2.2rc1 release.
2001-08-30: updated for proftpd-1.2.2 release, added functionality.
2001-10-20: updated for proftpd-1.2.4 release, added functionality.
2002-01-10: fixed mergedown problem
2002-01-11: corrected problem with parse_max_nbytes()
---------------------------------------------------------------------------
Affected Files
---------------------------------------------------------------------------
modules/mod_xfer.c
------------------------------------------------------------------------------
който търси,намира...
松下電
но аз междувременно намерих обяснение на едно единствено място в целия интернет - не знам защо не са го включили в userguide:
-----------------------------------------------------------------------------
TJ Saunders <[email protected]>
2001-10-29
-------------------------------------------------------------------------
Problem
------------------------------------------------------------------------
Many FTP administrators would like to be able to place size limits on
any single file that a client might upload. Others, though less common,
would like to place similar size restrictions on the size of files
downloaded from their servers.
----------------------------------------------------------------------------
Solution
----------------------------------------------------------------------------
Create two new configuration directives, MaxRetrieveFileSize (for
download restrictions) and MaxStoreFileSize (for upload restrictions).
Syntax: MaxRetrieveFileSize number|"*" units ["user"|"group"|"class" expression]
Default: Unlimited
Context: server config, <VirtualHost>, <Anonymous>, <Global>,
<Directory>, .ftpaccess
Module: mod_xfer
Compatibility: 1.2.4 and later
When downloading files to clients (eg serving a RETR request), the
server will check for any configured limit against the size of the file
being requested, and abort any transfers if the requested file's size
exceeds the configured limit.
A single "*" argument configures unlimited file sizes, and is used
primarily to override any inherited restrictions from higher contexts.
The given number is the number of bytes for the limit, and is followed
by a units specifier of (case-insensitive) "Gb" (Gigabytes),
"Mb" (Megabytes), "Kb" (Kilobytes), or "B" (bytes). The given number of
bytes is multiplied by the appropriate factor.
The optional parameters are used to restrict the file size limits only
to specific users. If the "user" restriction is given, then expression is a
user-expression specifying to which users the rule applies. Similarly for the
"group" restriction. For the "class" restriction, the expression is simply
the name of connection class for whom the rule will apply. If no matching
user, group, or class expression is found for the current user (in that
order), then a limit with no expression (ie no "user", "group", or "class"
identifier) is applied.
Examples:
# restrict downloads to only 1 gigabyte
MaxRetrieveFileSize 1 Gb
# restrict downloads for user fred, but allow unlimited download size for
# everyone else
MaxStoreFileSize 50 Kb user fred
MaxStoreFileSize *
See Also: MaxStoreFileSize
-----------------------------------------------
Syntax: MaxStoreFileSize number|"*" units ["user"|"group"|"class" expression]
Default: Unlimited
Context: server config, <VirtualHost>, <Anonymous>, <Global>,
<Directory>, .ftpaccess
Module: mod_xfer
Compatibility: 1.2.4 and later
When uploading files from a client (eg serving a STOR request), the
server will check for any configured limit against the size of the file
being sent, and abort any transfers if/when the given file's size
exceeds the configured limit.
A single "*" argument configures unlimited file sizes, and is used
primarily to override any inherited restrictions from higher contexts.
The given number is the number of bytes for the limit, and is followed
by a units specifier of (case-insensitive) "Gb" (Gigabytes),
"Mb" (Megabytes), "Kb" (Kilobytes), or "B" (bytes). The given number of
bytes is multiplied by the appropriate factor.
The optional parameters are used to restrict the file size limits only
to specific users. If the "user" restriction is given, then expression is a
user-expression specifying to which users the rule applies. Similarly for the
"group" restriction. For the "class" restriction, the expression is simply
the name of connection class for whom the rule will apply. If no matching
user, group, or class expression is found for the current user (in that
order), then a limit with no expression (ie no "user", "group", or "class"
identifier) is applied.
Examples:
# restrict upload to only 3 megabytes
MaxStoreFileSize 3 Mb
# restrict anonymous uploads to 50k, but allow unlimited upload size for
# everyone else
MaxStoreFileSize 50 Kb user anonymous
MaxStoreFileSize *
See Also: MaxRetrieveFileSize
----------------------------------------------------------------------------
Comments
----------------------------------------------------------------------------
Patch updated as of 2001-10-29 (1.2.4 release). Note that the directive
syntax has changed slightly (units specifier is now separate from the
number, and is a required argument).
Patch updated as of 2001-03-01 (1.2.1 release)
If/when this patch is accepted into the official source tree, or there
is a large user demand, I'll generate documentation patches.
Patch updated to work correctly on FreeBSD platforms, which had trouble
with the SIZE_MAX macro. Thanks to Vladimir Kotal <[email protected]>
for the bug report and fix.
2001-03-29: updated for recent proftpd-1.2.2rc1 release.
2001-08-30: updated for proftpd-1.2.2 release, added functionality.
2001-10-20: updated for proftpd-1.2.4 release, added functionality.
2002-01-10: fixed mergedown problem
2002-01-11: corrected problem with parse_max_nbytes()
---------------------------------------------------------------------------
Affected Files
---------------------------------------------------------------------------
modules/mod_xfer.c
------------------------------------------------------------------------------
който търси,намира...
松下電