About VLS Server
Bill Eldridge
bill at rfa.org
Sat Jun 15 16:23:44 CEST 2002
tamimi tareq wrote:
> '2002-06-15 11:59:17 [INFO/Vls] Starting input
> 'local1
> 2002-06-15 11:59:17 [ERROR/Vls] Unable to start input
> 'local1': Error: local1:
> Unable to initialise input: aborting
> Error: Parsing of file 'C:\vls/input.cfg' failed
> Error: Could not open file 'C:\vls/input.cfg': The
> system cannot find the path s
> .pecified
I'm not sure of details for running vls on
Windows, but basically vls.cfg tells vls
where to look for the configuration for
that input, and you probably have:
BEGIN "local1"
#ConfigPath = "/path" # where to find the "path/input.cfg"
ConfigPath = "C:\vls"
END
and vls is adding on "/input.cfg", which is fine for Unix, not
for Windows. If you leave out ConfigPath completely
it might find the file itself.
If you compiled this yourself, the value is in
src/modules/localinput/localinput.cpp, where
you can change the 2
+ "/input.cfg
to
+ "\input.cfg
though, again, I don't know the rest of the details
on vls pathhandlingin Windows.
--
Bill Eldridge
Radio Free Asia
bill at rfa.org
--
This is the vls-devel mailing-list, see http://www.videolan.org/vls-devel/
To unsubscribe, please read http://www.videolan.org/lists.html
If you are in trouble, please contact <postmaster at videolan.org>
More information about the vls-devel
mailing list