How to install LineControl Server for Linux ------------------------------------------- Prerequisites: - libpam (inclusive developmentfiles, e.g. header files) or libcrypt (you can't use crypt with MD5 passwords!) If you don't use user accountig it should be possible to work without one of those libs (crypt/pam). See './configure --help' for details. - gcc and gnu make - already working ppp / cable and/or *-DSL setup, that means you have to be able to call script 'foo' to dial and script 'bar' to hangup. It doesn't matter what script foo and bar do. They just have to bring a line up and down. For certain configs you're going to change them or writing wrapper scripts for them (e.g. 'con_type file'). More about this later. 1. untar the archive (e.g. 'tar -xvzf linesrv-2.1.2.tgz'). Then 'cd linesrv-2.1'. You've probably already done this :) Now go on: './configure' (you might want to read the bottom lines of './configure --help') 'make' If you got errors: Oops... not good. 2. The binaries are: ./server/linesrv the LineControl server Optional binaries: ./lclog/lclog logfile parser to use with the cgi of a webserver ./htmlstatus/htmlstatus Special, nice thing: read htmlstatus/README Configfiles / examples: ./server/config/* ./server/config/complete_syntax/linesrv.conf Here you should be able to find all possible config keywords. DONT USE 'make install' !! (Maybe it works, I didn't configure and test it!) 3. if everything compiles well, put the executable linesrv somewhere in your filesystem. 4. take a deep breath... 5. Get the file ./server/config/complete_syntax/linesrv.conf change it to suit your system and save it as /etc/linesrv.conf You can take any other sample configuration out of the ./server/config directory. In ./server/config/complete_syntax/linesrv.conf every possible keyword and the syntax are/should be explained. Run it: 6. execute linesrv. It should find the /etc/linesrv.conf and display something like the following (depends on the configuration of course!): --8<----------------------------------------- sci@sci:/data/src/cvs/linesrv-2.1/server/config > ../linesrv ... config dump ... sci@sci:/data/src/cvs/linesrv-2.1/server/config > --8<--------------------------------------- You will get the shell prompt after linesrv became a daemon. You won't see linesrv except with 'ps ax' (or 'ps x'). If the last two lines look like --8<--------------------------------------- Could not bind to socket: bind(): 98 LineControl Server not started. --8<--------------------------------------- linesrv probably runs already. (so don't tell me "I wasn't able to start linesrv...") If it doesn't already run, so wait a few minutes or restart your linux and try again. (we have to wait for the TCP ports/sockets to become free) Using it: 7. The server should run now if you were able to start and stop your internet connection with the given script before. So just get a client and test the whole thing. Have a look at your syslog... :) 'tail -f /var/log/messages' (at least on my system) on a debian using syslogng you try better 'tail -f /var/log/daemon | grep linesrv' 8. To terminate linesrv don't kill it with -9 or so. use 'kill -QUIT <process-id>' or 'kill -TERM <process-id>' instead. That's important because like this linesrv will try to close open connections and throws the clients out with a message instead of just closing the tcp connection. With SIGQUIT some logfile-entries get generated too... Good luck... let me know if you get real problems. S. Fuchs linecontrol@gmx.ch