Are you sure you want to update a translation? It seems an existing Japanese Translation exists already. However, the english version is more up to date.
We appreciate your interest in having Red Hat content localized to your language. Please note that excessive use of this feature could cause delays in getting specific content you are interested in translated.
We are generating a machine translation for this content. Depending on the length of the content, this process could take a while. Using -limit option, you can also limit the number of concurrent process that can be running. This helps xinted to avoid process table over-flow.
The following example will perform xinted internal state consistency check every two minutes seconds as specified in the -cc option. For debugging purpose, sometimes you may want to create an internal dump file of the current state of the xinetd. The above command will dump the xinted. If the "server" attribute is specified, this attribute takes priority.
This means you can have a telnet server listening on a local, secured interface, and not on the external interface. Or one port on one interface can do something, while the same port on a different interface can do something completely different. This banner is printed regardless of access control. In paticular, if the protocol requires CR-LF pairs for line termination, you must supply them.
This banner is printed as soon as access is granted for the service. This banner is printed immediately upon denial of access. This is useful for informing your users that they are doing something bad and they shouldn't be doing it anymore.
This specifies the maximum instances of this service per source IP address. This can also be specified in the defaults section. Takes two arguments. The first argument is the number of connections per second to handle. If the rate of incoming connections is higher than this, the service will be temporarily disabled.
The second argument is the number of seconds to wait before re-enabling the service after it has been disabled. The default for this setting is 50 incoming connections and the interval is 10 seconds.
For example: 2 or 2. The service will stop accepting connections at this load. This is the one minute load average. This feature is only avaliable if xinetd was configured with the -with-loadavg option. If the groups attribute is set to "yes", then the server is executed with access to the groups that the server's effective UID has access to.
Alternatively, if the group attribute is set, the server is executed with access to the groups specified. If the groups attribute is set to "no", then the server runs with no supplementary groups. This attribute must be set to "yes" for many BSD systems. This attribute can be set in the defaults section as well. On systems that support mdns registration of services currently only Mac OS X , this will enable or disable registration of the service. This defaults to "yes". Expects an octal value.
This option may be set in the "defaults" section to set a umask for all services. This is the umask that will be inherited by all child processes if the umask option is not used. This will enable only the services listed as arguments to this attribute; the rest will be disabled. If you have 2 ftp services, you will need to list both of their ID's and not just ftp.
It might accidentally be the ID, but you better check. Note that the service "disable" attribute and "DISABLE" flag can prevent a service from being enabled despite being listed in this attribute. The file is then parsed as a new configuration file. It is not the same thing as pasting the file into xinetd. The included file must be in the same form as xinetd. This may not be specified from within a service.
0コメント