One other thing.. there is a setting which will increase/disable the
timeout. The default is pretty short if you are a human trying to type
something.. :)
#This will disable it completely
set("server.timeout",-1.0)
Nick
On Fri, Oct 30, 2015 at 11:51 AM, [email protected] <[email protected]
> wrote:
> Hi Set, thanks for the reply,
>
> After so many hours I finally found out that I was actually connected
> when the cursor was blinking on the next line of the shell, and was
> timing out after 30
> seconds because of the liquidsoap setting server.timeout
> There is no welcome message or success message so it really didn't cross
> my mind at first.
>
> Now concerning the ownership and permissions of the file, by default
> liquidsoap creates it with 600 permissions (owner:read/write) because of
> the default setting set('log.file.perms', 384) and the user I connect to
> the shell is the owner of that liquidsoap process, so I never got an
> error about that.
>
> I also hope this helps someone else facing the same :)
>
>
> On 10/30/2015 01:42 PM, Set Hallstrom wrote:
> > On 2015-10-30 04:38, [email protected] wrote:
> >> Hello,
> >>
> >> First of all, congrats for the great software, it works great on my
> >> debian server, but I am having trouble connecting to the unix interface.
> >>
> >> I have followed the instructions described here under the "Securing the
> >> server" section:
> >> http://liquidsoap.fm/doc-svn/server.html
> >>
> >> restarting liquidsoap indeed creates the socket file with 600
> >> permissions but running the following command:
> >> socat /tmp/socket -
> >>
> >> I get this on cli:
> >> Connection timed out.. Bye!
> >>
> >> and in the liquidsoap log I get this:
> >> 2015/10/30 05:12:00 [server:3] New client unix socket "\253\214*\127".
> >> 2015/10/30 05:12:30 [server:4] Timeout reached while communicating to
> >> client unix socket "\253\214*\127".
> >> 2015/10/30 05:12:30 [server:3] Client unix socket "\253\214*\127"
> >> disconnected.
> >>
> >> Any help on this would be greatly appreciated
> >> Thanks !
> >>
> > I am not an expert, but the shell being the invocation of the the socat
> > command (/usr/local/bin/liq_shell) is supposed to exit if the file is
> > not readable and writeable. Maybe the socket file is deleted from /tmp/?
> > Also if, the socket-file belongs to the liquidsoap user with permission
> > 600, it might not be readble nor writable from the user you are loged in
> > with.
> >
> > Hope it may help and that more experienced users will help you better!
> > Best of luck!
> >
> > *Set
> >
> >
> ------------------------------------------------------------------------------
> > _______________________________________________
> > Savonet-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/savonet-users
> >
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Savonet-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/savonet-users
>
------------------------------------------------------------------------------
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
