Today (Saturday) We will make some minor tuning adjustments to MySQL.

You may experience 2 up to 10 seconds "glitch time" when we restart MySQL. We expect to make these adjustments around 1AM Eastern Daylight Saving Time (EDT) US.

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

SunOS 5.10 - man page for asadmin-create-lifecycle-module (sunos section 1as)

asadmin-create-lifecycle-module(1AS)				   User Commands			      asadmin-create-lifecycle-module(1AS)

create-lifecycle-module - adds a lifecycle module
create-lifecycle-module --user admin_user [--password admin_password] [--host localhost] [--port 4848] [--secure|-s] [--passwordfile file- name] [--terse=false] [--echo=false] [--interactive=true] --classname class_name [--classpath classpath] [--loadorder load_order][--fail- urefatal=false] [--enabled=true] [--description description ][--property (name=value)[:name=value]*] module_name Creates the lifecycle. This command is supported in remote mode only.
--user authorized domain application server administrative username. --password password to administer the domain application server. --host machine name where the domain application server is running. --port port number of the domain application server listening for administration requests. --secure if true, uses SSL/TLS to communicate with the domain application server. --passwordfile file containing the domain application server password. --terse indicates that any output data must be very concise, typically avoiding human-friendly sentences and favoring well- formatted data for consumption by a script. Default is false. --echo setting to true will echo the command line statement on the standard output. Default is false. --interactive if set to true (default), only the required password options are prompted. --classname fully qualified name of the startup class. --classpath indicates where this module is actually located if it is not under applications-root. --loadorder an integer value that can be used to force the order in which deployed lifecycle modules are loaded at server startup. Smaller numbered modules get loaded sooner. Order is unspecified if two or more lifecycle modules have the same load-order value. --failurefatal if true indicates abort server startup if this module does not load properly. --enabled determines whether the resource is enabled at runtime. --description text description of the resource. --property optional attribute name/value pairs for configuring the resource.
module_name unique identifier for the deployed server lifecycle event listener module. Example 1: using create-lifecycle-module asadmin> create-lifecycle-module --user admin --password adminadmin --host fuyako --port 7070 --classname "com.acme.CustomSetup" --classpath "/export/customSetup" --loadorder 1 --failurefatal=true --description "this is a sample customSetup" --property rmi=Server="acme1\:7070":timeout=30 customSetup Command create-lifecycle-module executed successfully Where: customSetup is the lifecycle module created. The escape character (\) is used in the property option to distinguish the colons (:).
0 command executed successfully 1 error in executing the command asadmin-delete-lifecycle-module(1AS), asadmin-list-lifecycle-modules(1AS) J2EE 1.4 SDK March 2004 asadmin-create-lifecycle-module(1AS)

Featured Tech Videos