Closed daddyfix closed 3 years ago
Hi, I've the same problem and tried chmod 757 and 777 and 10777 /tmp/ with any effects. Always the same error. I'm using raspberry 4. My best lelis
My gwsocket worked well with Rpi 2. The option as _--pipein=<path/file>_gives the same error but mkfifo in my C program works well even for /tmp/ folder. Anyway, gwsocket is always stopped (bad address) and impossible to use. The best solution could be perhaps to comment this lines and recompile websocket.c but .......Any way I have to switch to Ajax, exec() in PHP and C brrrrrr. My Best lelis
I found out that version 0.3.0 works as expected I'm using that version for now and I will probably have to comment out the mkfifo check in version 0.4.0. thanks for your help I'm going to keep working on it and let you know what happens
On Thu., Jun. 10, 2021, 10:21 a.m. lelisele, @.***> wrote:
My gwsocket worked well with Rpi 2. The option as _--pipein=<path/file>_gives the same error but mkfifo in my C program works well even for /tmp/ folder. Anyway, gwsocket is always stopped (bad address) and impossible to use. The best solution could be perhaps to comment this lines and recompile websocket.c but .......Any way I have to switch to Ajax, exec() in PHP and C brrrrrr. My Best lelis
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/allinurl/gwsocket/issues/41#issuecomment-858664924, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABEIKU32XXWOBYH3X6WFQODTSDC6VANCNFSM46J7V2UA .
Could you please try passing --pipeout=<path>
. e.g.,
gwsocket --pipein=/tmp/wspipein.fifo --pipeout=/tmp/wspipeout.fifo
Seems like I'll need to address the default path. Let me know how it goes. Thanks
By the way, you can also try piping data in. e.g.,
tail -F /var/log/apache2/access.log | gwsocket --std --port 7890
Thanks allinurl for your help. These options gives the same error (bad address) with "my" folder. Do I need to test with /tmp/?. I've just finished to implement my C program to control serial UART via USB0 and would like to send some data from my web page directedly to C interface and external RealTime DSP target. That worked well in Rpi2 and now not really. I've tried mkfifo with address 0777 and was able to generate fifo in /tmp/
Pushed an update. It should solve the issue. There's no need for setting --pipein=/tmp/wspipein.fifo
--pipeout=/tmp/wspipeout.fifo
as it will use those paths as default.
Please rebase from origin and let me know how it goes.
That's great.. will do
On Thu., Jun. 10, 2021, 9:28 p.m. Gerardo O., @.***> wrote:
Pushed an update. It should solve the issue. There's no need for setting --pipein=/tmp/wspipein.fifo --pipeout=/tmp/wspipeout.fifo as it will use those paths as default.
Please rebase from origin and let me know how it goes.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/allinurl/gwsocket/issues/41#issuecomment-859193963, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABEIKU64HAHVD7PSKK452JTTSFRCDANCNFSM46J7V2UA .
A lot of thanks allinurl !!!!! For me it works. Bye, bye PHP and its exec() brrrr. lelisele
Pushed an update. It should solve the issue. There's no need for setting
--pipein=/tmp/wspipein.fifo
--pipeout=/tmp/wspipeout.fifo
as it will use those paths as default.Please rebase from origin and let me know how it goes.
After new build this date it works great on Raspberry Pi 4 (buster) Thanks
Great to hear that. Thanks for letting me know!
I built v 0.4.0 on Buster (Raspberry Pi 4 Model B Rev 1.1)
But I get this error when trying to pipein fifo. Any help would be appreciated
websocket.c - Line 2279+