If you want to use the telnet interface, running
VLS is very easy: just type vls in a shell
console, and that's all. Running vlsd will
start VLS as a daemon and will detach itself from the launching
shell. Remember that VLS will try to load its configuration file
(vls.cfg) from the current directory, and if
there is no vls.cfg there, it will try to load it
from SYSCONF_DIR/etc/videolan (see section Configuration)
.
If your log file is vls.log as
in the example, VLS will need write access in the current directory, or
you will see something like
:
*** Exception *** in copy constructor (0xbffffc98, copy of 0x80e30a8)
Unable to open the log file "vls.log": Error: Could not open file 'vls.log':
Permission denied
Remember also that you must be root when using the
"Interface" option in vls.cfg
.
If everything is right, you will see something like :
VideoLAN Server v 0.5.3 (Jun 6 2003) - (c)1999-2003 VideoLAN
2002-03-09 17:24:51 [INFO/Vls] Module "channel:file" registered
2002-03-09 17:24:51 [INFO/Vls] Module "channel:network" registered
2002-03-09 17:24:51 [INFO/Vls] Module "mpegreader:file" registered
2002-03-09 17:24:51 [INFO/Vls] Module "mpegconverter:ts2ts" registered
[...]
What you can see on the screen (stderr) is exactly
what goes in the log file vls.log
.
When VLS has been successfully started, it doesn't take any command from its standard input, so you can put it into background (you can use the screen utility to do that) .
On the other hand, if you want to use the command line interface, please see the VideoLAN HOWTO .