Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

lafe(6) [debian man page]

lafe(6) 							   Games Manual 							   lafe(6)

NAME
lafe - Latency Free Empire client SYNOPSIS
lafe country [password [host [port]]] DESCRIPTION
lafe is an empire client optimized for high latency links. You can type in, edit, and send several commands before the server replies with output from the first command. This allows you to make better use of the existing bandwidth than most other clients. pei and eif are par- ticularly susceptible to latency, as they require a complete exchange of data before prompting again. lafe could also be called LAg Free Empire. Empire 2 asynch features are supported. Empire 3 C_SYNC isn't supported, as this is a rather dumb client (in between emp_client and eif) and C_SYNC was removed from Empire 4 (Wolfpack). Readline is supported, and at the moment required. If you want lafe without readline, use emp_client instead. Parameters country If the only parameter this is use as a key to look up the game name as specified by the addgame commands in the $HOME/.laferc file. Otherwise it is used as the country name on the server. Defaults to 'visitor' if unspecified. password defaults to 'visitor' if unspecified. host defaults to 149.84.128.9 if unspecified. port defaults to 6667 if unspecified. Local commands help print syntax summary of local commands. addgame game country password host port logfile directory add a game definition for the "lafe game" startup method. execute Handles exec scripts locally runfeed Runs the argument as a shell command, and sends the output to the server shell Run the argument as a shell script alias Print, delete, or define an alias. Use single quotes around the alias definition to protect $*, $1, $2, ... setvar Set, delete, or print local variables. shell Run parameters in a subshell. history print the previous commands. verbose toggle verbosity of message. "verbose on" if you want all the error messages, C_SYNC messages, etc. Off by default. waitsync Wait for all responses from server before proceeding. Useful in scripts before a runfeed or shell command. ENVIRONMENT
Environment variables are supported for backward compatibility with emp_client. This information is best placed in the $HOME/.laferc file using the addgame command. EMPIREHOST hostname of server EMPIREPORT TCP/IP port number of server COUNTRY Country name to log in as REPRESENTATIVE Password for country FILES
$HOME/.laferc contains any valid local commands to run before connecting to a server. SEE ALSO
emp_server(6), emp_client(6), emp_hub(6), pei(6), eif(6), http://wolfpackempire.com/ BUGS
Output redirection does not work with aliases and internal commands. Simultaneous connection to multiple servers is not yet supported. Version 1.0 addresses both of these issues, but has stalled due to lack of time. When typing well ahead of the server, lafe must guess whether a local command should be parsed locally or forwarded to the server (as part of a telegram for instance). It guesses local, which is not always correct. This is the price you pay for speed. AUTHOR
This manual page was written by Drake Diedrich <dld@debian.org> lafe(6)

Check Out this Related Man Page

asadmin-delete-instance(1AS)					   User Commands				      asadmin-delete-instance(1AS)

NAME
delete-instance - deletes the instance that is not running. SYNOPSIS
delete-instance [--user admin_user] [--password admin_password] [--host localhost] [--port 4848] [--local=false] [--domain domain_name] [--passwordfile filename] [--secure|-s]instance_name Use the delete-instance command to delete the instance that you specify. The delete-instance command can be run both locally and remotely. To delete the instance locally, not requiring the administration server to be up and running, specify the --local option. To delete the instance remotely, the administration server must be running on the hostname and port number specified. The user authenticates using the password identified for the administration server. Additionally, the instance must already exist within the domain served by the adminis- tration server. Use this command with discretion since it is destructive and there is no undo. OPTIONS
--user administrative user associated for the instance. --password administrative password corresponding to the administrative user. --host host name of the machine hosting the administrative instance. --port administrative port number associated with the administrative host. --domain name of the domain. --local determines if the command should delegate the request to administrative instance or run locally. --passwordfile file containing passwords appropriate for the command (e.g., administrative instance). --secure if true, SSL/TLS to communicate with the administrative instance. OPERANDS
instance_name name of the instance to be deleted. Example 1: Using delete-instance in local mode asadmin> delete-instance --domain domain1 server1 Deleted Instance server1 successfully Where: the server1 instance for the domain1 domain is deleted on the local machine. Example 2: Using delete-instance in remote mode asadmin> delete-instance --user admin --passwordfile passwords.txt --host localhost --port 4848 server1 Deleted Instance server1 successfully Where: the server1 instance for the domain associated with the specified user, passwords in the password file, host, and port number is deleted on the remote machine. EXIT STATUS
0 command executed successfully 1 error in executing the command INTERFACE EQUIVALENT
Server Instance page asadmin-create-instance(1AS), asadmin-start-instance(1AS), asadmin-stop-instance(1AS), asadmin-restart-instance(1AS) J2EE 1.4 SDK March 2004 asadmin-delete-instance(1AS)
Man Page