Fetching latest commit…
Cannot retrieve the latest commit at this time
|Failed to load latest commit information.|
Dependencies: -- asciidoc, http://www.methods.co.nz/asciidoc (package: asciidoc), to create documentation in different formats (man, pdf, html) NOTE: The distribution tar contains the doc in all available formats, so you don't need asciidoc to make and install procServ. -- libtelnet, http://github.com/seanmiddleditch/libtelnet (package: libtelnet) NOTE: The distribution tar contains the libtelnet sources, so it will be compiled into procServ automatically, if not found. procServ is on GitHub, distribution also through SourceForge: https://github.com/ralphlange/procServ http://sourceforge.net/projects/procserv/ Continuous Integration builds provided by CloudBees: https://openepics.ci.cloudbees.com/view/procServ/ procServ is part of official Linux distributions: Debian/Ubuntu -- apt-get install procserv Fedora/RHEL -- yum install procServ The Git source repository contains the packaging extras, which are not part of the distribution tar. Building within an EPICS build system Unpack procServ at the appropriate place within your EPICS structure. Inside that directory, run ./configure --with-epics-top=TOP where TOP is the relative path to the structure TOP. (For a structure created with epicsMakeBaseExt.pl, the appropriate place for the procServ subdir would be under TOP/src, with ../.. being the relative path to specify to configure - which is the default.) Building from procServ Git repository Requires autoconf >=2.61, automake >= 1.10 Optional asciidoc >= 8.4, FOP >= 0.95, xsltproc >= 1.1.24 $ git clone https://github.com/ralphlange/procServ.git $ cd procserv $ make $ ./configure --enable-doc $ make Note: When building from the repository you must explicitly use --enable-doc or --disable-doc. Omitting this option assumes the distribution behaviour, that the documentation should be installed, but doesn't need to be built. Using procServ to run EPICS soft IOCs in a production environment Michael Davidsaver (BNL) has created SysV-style rc scripts to configure and run EPICS soft IOCs using procServ. See http://epics.nsls2.bnl.gov/debian/ for the Debian package or https://github.com/epicsdeb/sysv-rc-softioc for the git repository. Using procServ on Windows Under Windows, procServ compiles in a Cygwin environment. Configure with '--enable-access-from-anywhere' and run with '--allow' to allow remote access to the child console. The executable is available for download on SourceForge. To run on a non-Cygwin Windows system, procServ only needs Cygwin1.dll, e.g. in the same directory as the executable. Caveats: * Use Windows path delimiters '\' specifying the child executable, to avoid permission bit warnings/errors. * Under command.com, the caret sign '^' has to be escaped using '^^'. * Forking the daemon currently does not exit the foregroud process, resulting in an additional procServ process. This is a known issue and currently being investigated. Enjoy!