2d41198b3e
Files correlati : Ricompilazione Demo : [ ] Commento : Progetti e altra roba per Linux git-svn-id: svn://10.65.10.50/trunk@11293 c028cbd2-c16b-5b4b-a496-9718f37d4682
88 lines
3.1 KiB
Plaintext
Executable File
88 lines
3.1 KiB
Plaintext
Executable File
|
|
=========================================================================
|
|
HL-Server for Linux 11/2002
|
|
=========================================================================
|
|
|
|
|
|
General/Introduction
|
|
====================
|
|
|
|
HL-Server for Linux provides the same functionality as HL-Server for
|
|
Win32 (HLS32 and HLS32SVC) and HL-Server NLM. An application using the
|
|
HL-Server cannot recognize any difference between them. The Hardlocks
|
|
used are the same, so you can select the HL-Server that fits best into
|
|
your customers network environment. HL-Server for Linux supports IP/UDP
|
|
protocol and uses port 3047 (IANA-registered) for communications.
|
|
|
|
Using a demo Hardlock (module address 29809), you can test the HL-Server
|
|
without needing an HL-Server-Hardlock.
|
|
|
|
HL-Server can be started as a daemon (option -d) or as a console
|
|
application (-a). Console application mode can be used to track down
|
|
possible problems; it shows a trace of all client requests, similar to
|
|
the trace show by HLS32.EXE on Win32 after double clicking the Hardlock
|
|
Icon.
|
|
|
|
HL-Server for Linux can be watched and administered by AKSMON (Aladdin
|
|
Monitor) running on a Win32 machine; AKSMON itself does not run on Linux.
|
|
|
|
HL-Server for Linux also fully implements LiMaS and supports all
|
|
available HL-Server types (USB, parallel, internal).
|
|
|
|
|
|
Starting HL-Server for Linux
|
|
============================
|
|
|
|
Before HL-Server for Linux can be started, the Hardlock drivers
|
|
(aksparlnx.o and aksusbd) must be installed. Please consult the
|
|
install.txt file of the Hardlock driver for information.
|
|
|
|
HL-Server is started from the console with
|
|
|
|
hlserver [options]
|
|
|
|
The following options are supported:
|
|
|
|
-h display help
|
|
-a run as application (not as daemon)
|
|
-d run as daemon
|
|
-module:n[,m] module address [,max logins] of Hardlock (up to 10 times)
|
|
(optional, modules are auto-added when requested)
|
|
-timeout:n timeout value in minutes (1..9999, 0=none, default=15)
|
|
-zombie enable zombie mode for timed out logins
|
|
|
|
(all parameters may be abbreviated by their first letter)
|
|
|
|
You must specify at least the -a or -d option.
|
|
|
|
Examples:
|
|
|
|
hlserver -d
|
|
|
|
HL-Server starts as a daemon without registering any Hardlock.
|
|
Whenever a client application request an unknown Hardlock, HL-Server
|
|
looks for that Hardlock and adds it automatically, if available.
|
|
|
|
It is recommended to insert "hlserver -d" into the appropriate
|
|
startup script of the machine.
|
|
|
|
The daemon writes its start/stop events and adding/removing of
|
|
a hardlock to the syslog (normally in /var/log/messages).
|
|
|
|
hlserver -m:29809 -d
|
|
|
|
HL-Server starts as a daemon and tries to register Hardlock 29809.
|
|
If the Hardlock is not found, the daemon stops immediately.
|
|
|
|
|
|
Stopping the HL-Server
|
|
======================
|
|
|
|
The daemon is stopped as usual by "kill <processid>".
|
|
(HL-Server uses Posix threads, so it appears several times in the process
|
|
list; just kill the first thread, the others stop automatically.)
|
|
|
|
The application can be stopped with ^C.
|
|
|
|
|