Special option for the SYS V start / stop scripts | ||
start |
The server will be started. start may be ommited |
|
stop |
An running server will be stopped |
|
status |
This allow to ask if a server is running. |
|
|
||
Normal options | ||
-dev |
device file |
This option is mandatory and is also used in order to get the status
or to stop a running server.
Device file is the name of the character device on which the printer is attached (/dev/lp0, /dev/usb/lp0, /dev/ecpp0, ...) |
-nodaemon |
This option is for test purpose, without this option mtink start in the background. |
|
-model |
model name |
If the printer don't return it identity you may tell which printer is attached.
The name is derived from the official name and space characters are to be replaced by the "_ "
character. This will be the case for the Stylus Scan 2500 (model anme isScan_2500).
This option may also be usefull for multifunction device as the Stylus Photo 895 under Linux. If the printer is powered off and then on, the usb kernel will not detect the printer properly and mtinkd must be at least stopped and started again. |
-name |
name |
The name of the named pipe will be set according to this name. If the -model
option is not given, mtinkd will terminate if the identification returned don't comply with
passed name |
-usbbase |
path and device file base |
ONLY FOR LINUX This option require a special system call which is only
implemented into newer kernels.
The -type <name> option is required ! path and device file base may be /usr/usblp or /usr/usl/lp. All device files matching whith the passed name will be scanned for the wanted printer, the device file will then be used later. If the kernel don't support the special call, scanning will fail and if the -dev <device file> option was given, the given device file name will then be used. |
If you configure your print systeme you must choose the file /var/mtink/xxx. If you don't use cups you must make sure that the print system will not write at the same time on the named pipe ! Call of ttinkNormally you have to call ttink with for example the option -d /dev/lp0. If you use the mtinkd server you must launch ttink with the option -d /var/mtink/lp0Call of mtinkMtink can be called as usual. If the choosed device is locked, mtink will allow you to choose the /var/mtink/* files.Theory of operationMtinkd and mtink / ttink communicate via shared memory. The shared memory will be created by the server process and this memory has a key which is calculated from the file name /var/mtink/<name>. The print jobs are to be send to the file /var/mtink/<name>. If datas are recognized by mtinkd on this file, these datas are packed into the D4 protocol and sent to the printer via a data channel. Queries or commands from mtink / ttink are written into the shared memory and send via the D4 control channel. Both channel data and control channel are independant so you will be able to get information while a print job is running.In order to prevent problems, only one frontend (mtink or ttink) can attach it to the server mtinkd. Linux specific: Powering the printer on / off / on will normally be handled by mtinkd however the usb driver may be the cause of problems id the attached device contain more as one device as printer and storage. In this case you will have to stop the daemon and restart it. If this don't help you must delete the printer module and insert it again. Start of mtinkd at boot timeIn order to allow an easy integration of the daemon to different systems the options start, status and stop was added to the daemon mtinkd. This allow a dramatic simplification of the start script. An example script is provided in the source subdirectory etc:
|