>I would be all in favour foradding a new command that actually terminates the whole of FluidSynth.“shutdown” might be an appropriate name. :-)It seems that this "shutdown" command simply should only terminate the server (and consequently close all client connection) ?envoyé : 7 mars 2022 à 00:1
Am So., 6. März 2022 um 23:34 Uhr schrieb Marcus Weseloh :
> I just tried it with 2.2.1 and got the same result: when I type
> "quit", FluidSynth doesn't exit but waits for the accept() to return.
> And I don't see any ifdefs for WIN32 around this call... really weird.
> Is Windows handling thread
Am So., 6. März 2022 um 19:31 Uhr schrieb Ben Gonzales via fluid-dev
:
> I start my FS server with the --no-shell option, then telnet in and out
> of the running server many times during a session with no problems. I am
> running RPi OS. I assume Marcus' example is starting with an active
> shell (
e command on the remote terminal talking with the
fluidsynth server works fine. The remote "quit" command works fine too.
envoyé : 6 mars 2022 à 14:13de : Marcus Weseloh
à : FluidSynth mailing list
objet : Re: [fluid-dev] Failure to bind server socket: 98
Am So., 27. Feb. 2022 um 17:30 U
Sorry , there is a typos mistake on my previous message:The fluidsynth version is 2.2.1 (not 2.1.1).envoyé : 6 mars 2022 à 17:50de : Ceresa Jean-Jacques à : FluidSynth mailing list objet : Re: [fluid-dev] Failure to bind server socket: 98 >It seems we even have a bug in the handling of
>It seems we even have a bug in the handling of the interactive andsocket shell connections. If I start FluidSynth with -s and type“quit” in the interactive shell, then the program hangs and does notreturn to the command prompt.On Windows, with fluidynth v2.1.1 starting fluidsynth with -s and typ
Am So., 27. Feb. 2022 um 17:30 Uhr schrieb Ben Gonzales via fluid-dev
:
>
> So, is there a shell command to shut down the program (rather than just
> exit the shell)
>
> If not, how do I shut it down elegantly without killing the process
> (which is what I am doing currently)?
Good question! I thi
So, is there a shell command to shut down the program (rather than just
exit the shell)
If not, how do I shut it down elegantly without killing the process
(which is what I am doing currently)?
Ben
On 25/2/22 09:21, Marcus Weseloh wrote:
Am Do., 24. Feb. 2022 um 23:09 Uhr schrieb :
It's s
Am Do., 24. Feb. 2022 um 23:09 Uhr schrieb :
> It's standard UNIX sockets behaviour unless the code specifies the
> SO_REUSEADDR socket option. It's a security mechanism to stop a new
> program taking over an old program's socket and receiving any new
> packets or connections intended for the old p
On 25/2/22 08:50, Ben Gonzales via fluid-dev wrote:
Hi all.
I'm running FS on a RPi4, but I get this problem with all other
versions of Pi I've tried.
I"m using Telnet to communicate with the running server. When I shut
down the server, to make program changes, and restart it quickly I get
Hi all.
I'm running FS on a RPi4, but I get this problem with all other versions
of Pi I've tried.
I"m using Telnet to communicate with the running server. When I shut
down the server, to make program changes, and restart it quickly I get
this error, and the server fails to start:
fluidsyn
11 matches
Mail list logo
