VTQLserver
[options] socket_name
VTQLserver $HOME/.vtql-socket.root
VTQLserver -- -socket_name_with_dash
-h,--help | show help text and exit |
-v,--version | show some version info and exit |
-u,--user name | run as user name |
-g,--group name | run as group name |
-- | force the next option to be interpreted as socket_name |
socket_name | The filename of the socket, that will be opened by the server on start. |
You should not run the server as root, since this there may be exploits to VTQLserver. So if you start VTQLserver as root, you have to specify a user name or user ID for the server's process (the name may also be "root", by the way).
The socket will be in configruation mode
and any fruther configuration of the server is done via this socket. The server
will fork itself into background after the socket was sucessfully opend.
VTQLserv_start
You may either use this script as startup script or you may use it as SYSV
startup script (i.e. let VTQLserver run as deamon in specific runlevels): Put
it into "/etc/rc.d/init.d
" and link it properly into the
"/etc/rc.d/rc?.d
" directories (read "man 8 init
" if you do not know about the SYSV startup process).
You may have to edit the "--config--
" section of the
script to get it running.
VTQLserv_start
option
start | Try to start a server |
stop | Try to kill the server |
The script looks for a configuration file first at
$HOME/.VTQL
, second at /etc/VTQLrc
and starts and
configures the server. Any socket configured in query or event mode is made accessable for any
user.
The configuration file VTQLrc
The configuration file is quite simular to the one of xawtv, in special, the station
settings are almost the same, so it should not be too hard to write the
configuration file. A full documentation is provided at the example file
"scripts/VTQLrc
" in your source directory. If you try to
do advanced things in that configuration file or even stuff, that is beyond
that configuration file, you may have to understand a bit of VTQL.