Re: [fpc-devel] Linux Binary - Socket Output affected by SystemCtl, HELP!

2020-01-29 Thread Marco van de Voort
Op 29/01/2020 om 14:54 schreef Ozz Nixon via fpc-devel: Would/Could, LANG/LOCALE affect socket output? * I personally do not touch environment variables - so I am not sure what to ever try. The "client" (Telnet) I have tried Terminal.App, iTerm2, Putty.exe, Telnet.exe, xTerm-256, fTelnet,

Re: [fpc-devel] Linux Binary - Socket Output affected by SystemCtl, HELP!

2020-01-29 Thread wkitty42
On 1/29/20 8:54 AM, Ozz Nixon via fpc-devel wrote: Would/Could, LANG/LOCALE affect socket output? wouldn't they affect what the server decides to transmit based on the selected "character set"? -- NOTE: No off-list assistance is given without prior approval. *Please keep mailing

Re: [fpc-devel] Linux Binary - Socket Output affected by SystemCtl, HELP!

2020-01-29 Thread Ozz Nixon via fpc-devel
1. My code does not directly interact with any environment variables. 2. I am using version 2.6.4 to compile the daemon. my .service file for systemctl looks like: [Unit] Description=The Modern Pascal Code Running Socket Server After=network.target [Service] Type=simple

Re: [fpc-devel] Linux Binary - Socket Output affected by SystemCtl, HELP!

2020-01-29 Thread Ozz Nixon via fpc-devel
> That proves the problem is unrelated to sockets. Is is related to string/encoding handling. Now that makes a lot more sense than the socket doing goofy magic. The string layer in FPC doing goofy magic! I am trying your .sh script idea now... On Wed, Jan 29, 2020 at 9:42 AM Nikolai Zhubr via

Re: [fpc-devel] Linux Binary - Socket Output affected by SystemCtl, HELP!

2020-01-29 Thread Nikolai Zhubr via fpc-devel
Hi! 29.01.2020 18:07, Ozz Nixon via fpc-devel: 1. My code does not directly interact with any environment variables. Ok. ExecStart=/usr/local/bin/coderunner2 I'd suggest, as a quick and horrible temporary hack/test, replace this direct binary call with a shell wrapper, lets name it e.g.

[fpc-devel] Linux Binary - Socket Output affected by SystemCtl, HELP!

2020-01-29 Thread Ozz Nixon via fpc-devel
I am not sure how this is occurring, however, my socket daemon on Linux - is launched by hand ./program is able to send to the socket: Socket.Write(#218+#196+#191); And the terminal (any) will display the single highbit characters. If systemctl start myprogram... that same call sends '???'.

Re: [fpc-devel] Linux Binary - Socket Output affected by SystemCtl, HELP!

2020-01-29 Thread Ozz Nixon via fpc-devel
per units, coderunner uses: uses {$IFDEF UNIX} cthreads, baseunix, unix, {$ENDIF} { huge list of units I developed } variants, keyboard, PdfDocs, PdfTypes, PdfFonts, SQLDb, odbcconn, sqlite3conn, <-- soon to remove, it's unstable in our testing jansql, <-- soon to remove could not get it

Re: [fpc-devel] Linux Binary - Socket Output affected by SystemCtl, HELP!

2020-01-29 Thread Marco van de Voort
Op 29/01/2020 om 14:23 schreef Ozz Nixon via fpc-devel: I am not sure how this is occurring, however, my socket daemon on Linux - is launched by hand ./program is able to send to the socket: Socket.Write(#218+#196+#191); And the terminal (any) will display the single highbit characters. If

Re: [fpc-devel] Linux Binary - Socket Output affected by SystemCtl, HELP!

2020-01-29 Thread Marco van de Voort
Op 29/01/2020 om 16:07 schreef Ozz Nixon via fpc-devel: 1. My code does not directly interact with any environment variables. Unit cwstring and clocale might do on startup. This might influence e.g. widestring/unicodestring<-> ansistring conversions and back. 2. I am using version 2.6.4

Re: [fpc-devel] Linux Binary - Socket Output affected by SystemCtl, HELP!

2020-01-29 Thread Ozz Nixon via fpc-devel
Would/Could, LANG/LOCALE affect socket output? * I personally do not touch environment variables - so I am not sure what to ever try. The "client" (Telnet) I have tried Terminal.App, iTerm2, Putty.exe, Telnet.exe, xTerm-256, fTelnet, etc. all clients on all 3 OSes render '?' from the daemon if

Re: [fpc-devel] Linux Binary - Socket Output affected by SystemCtl, HELP!

2020-01-29 Thread Sven Barth via fpc-devel
Ozz Nixon via fpc-devel schrieb am Mi., 29. Jan. 2020, 16:51: > PS. Worsecase, I can scrap 2.6.4 for 3.0.x - just been waiting for a > stable LLVM build for all 3 OSes I support. > Then you're in for long wait as the LLVM backend is fully supported only on trunk (at least for macOS and Linux on

Re: [fpc-devel] Linux Binary - Socket Output affected by SystemCtl, HELP!

2020-01-29 Thread Ozz Nixon via fpc-devel
using the .sh concept: # systemctl status coderunner * coderunner.service - The Modern Pascal Code Running Socket Server Loaded: loaded (/usr/lib/systemd/system/coderunner.service; enabled; vendor preset: disabled) Active: active (running) since Wed 2020-01-29 10:55:30 EST; 8s ago Process:

Re: [fpc-devel] Linux Binary - Socket Output affected by SystemCtl, HELP!

2020-01-29 Thread Ozz Nixon via fpc-devel
I have waited this long now :-) I only run 2.6.4 as something I developed didn't work correctly when compiled with 3.0.0, 3.0.2... Ozz On Wed, Jan 29, 2020 at 10:11 AM Sven Barth via fpc-devel < fpc-devel@lists.freepascal.org> wrote: > Ozz Nixon via fpc-devel schrieb am Mi., > 29. Jan. 2020,

Re: [fpc-devel] Linux Binary - Socket Output affected by SystemCtl, HELP!

2020-01-29 Thread Nikolai Zhubr via fpc-devel
Hi! 29.01.2020 19:04, Ozz Nixon via fpc-devel: cat /etc/test.txt ls -alrt /etc/test.txt -rw-r--r-- 1 root root 0 Jan 29 10:54 /tmp/test.txt Make sure there is no naming confusion (such as e.g. /tmp/test.txt and /etc/test.txt unintentionally intermixed) Another point is that a binary