Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

gems-server(1) [debian man page]

GEMS-SERVER(1)							gems documentation						    GEMS-SERVER(1)

NAME

       gems-server - Transmit a shell session in real time.

SYNOPSIS

       gems-server [-ip ip] [-port p] [-maxconn n] [-wait m] [-log dest] [-noscript] [-script_bin script]

       gems-server -h | -v

DESCRIPTION

       Transmits a shell session to be shown in real time in various different computers or terminals.

       gems-server  transmits data in real time to clients via a network connection. Each one of these clients must run the gems-client(1) program
       to establish connection and receive the transmitted data. Clients can connect and disconnect at any given time, but  of	course	they  will
       only receive the data that is transmitted while they are connected (just like a radio transmission/reception system).

       The  gems  system is normally used to transmit a console session and show it in various computers at the same time, but it is also possible
       to transmit any other kind of data.

OPTIONS

       -ip    IP address where connections will be accepted.

       -port  TCP port. Default: 6666.

       -maxconn
	      Do not accept more than n simultaneous clients. Default: 25.

       -wait  Wait until m clients are connected before starting the transmission. This is useful to ensure that the first m clients will  receive
	      all data transmitted. The default behavior is to start transmission immediately, without waiting for client connections.

       -log   By  default,  the server does not write log messages. This option configures the destination of logs. The dest argument can be `sys-
	      log' (to log through syslogd(8)), `stderr' (to log through standard error output), or it can be an arbitrary filename (log  messages
	      will be appended to the file, if it exists).

       -noscript
	      By  default,  the  server  executes the script(1) program to take terminal data and transmit it. When this option is used the server
	      will not run script, and data will be read form standard input.

       -script_bin
	      Specifies the location of the script(1).	program. Default: /usr/bin/script.

       -h     Show a short help message.

       -v     Show version information.

FILES

       /var/lock/gems-server.PORT
	      Lock file.  gems-server creates this file on initialization and deletes it on exit. PORT is replaced by the TCP  port  used.   gems-
	      server will not run if this file is already present in the system.

AUTHORS

       Diego Essaya <dessaya@fi.uba.ar>

       Emiliano Castagnari <ecastag@fi.uba.ar>

SEE ALSO

       gems-client(1), script(1), syslogd(8)

gems								    AUGUST 2004 						    GEMS-SERVER(1)

Check Out this Related Man Page

BUNDLE-PACKAGE(1)														 BUNDLE-PACKAGE(1)

NAME

       bundle-package - Package your needed .gem files into your application

SYNOPSIS

       bundle package

DESCRIPTION

       Copy  all  of  the  .gem files needed to run the application into the vendor/cache directory. In the future, when running bundle install(1)
       bundle-install.1.html, use the gems in the cache in preference to the ones on rubygems.org.

GIT AND PATH GEMS

       In Bundler 1.0, the bundle package command only packages .gem files, not gems specified using the :git or :path options. This  will  likely
       change in the future.

REMOTE FETCHING

       By  default,  if you simply run bundle install(1) bundle-install.1.html after running bundle package(1) bundle-package.1.html, bundler will
       still connect to rubygems.org to check whether a platform-specific gem exists for any of the gems in vendor/cache.

       For instance, consider this Gemfile(5):

	   source "http://rubygems.org"

	   gem "nokogiri"

       If you run bundle package under C Ruby, bundler will retrieve the version of nokogiri for the "ruby" platform. If you deploy to	JRuby  and
       run bundle install, bundler is forced to check to see whether a "java" platformed nokogiri exists.

       Even  though  the nokogiri gem for the Ruby platform is technically acceptable on JRuby, it actually has a C extension that does not run on
       JRuby. As a result, bundler will, by default, still connect to rubygems.org to check whether it has a version of one of your gems more spe-
       cific to your platform.

       This  problem is also not just limited to the "java" platform. A similar (common) problem can happen when developing on Windows and deploy-
       ing to Linux, or even when developing on OSX and deploying to Linux.

       If you know for sure that the gems packaged in vendor/cache are appropriate for the platform you are on, you can run bundle install --local
       to skip checking for more appropriate gems, and just use the ones in vendor/cache.

       One  way to be sure that you have the right platformed versions of all your gems is to run bundle package on an identical machine and check
       in the gems. For instance, you can run bundle package on an identical staging box during your  staging  process,  and  check  in  the  ven-
       dor/cache before deploying to production.

								     June 2012							 BUNDLE-PACKAGE(1)
Man Page