So far in testing, looks like setting $TERM to xterm-256color resolved my issue. (not 100% sure if it was specifically that setting, but, after 20+ hours for a couple days in a row, it started working with that being defined in the .sh idea (thanks!)).
path typo was just my exhaustion... it is set to /tmp/test.txt ... per user pid, I am old school (risk taker), I shell in as root, and code/run as root. Have since 1997 when I started running Linux as my main server line...so not a permissions issue. ;-) off to bed... Thanks everyone for your input and ideas where/what to try! Monday should be a good day :-) On Wed, Jan 29, 2020 at 11:28 AM Nikolai Zhubr via fpc-devel < fpc-devel@lists.freepascal.org> wrote: > Hi! > > 29.01.2020 19:04, Ozz Nixon via fpc-devel: > > cat /etc/test.txt > > <null> > > 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 running from systemd context might have > somewhat different access rights as compared to running from an > interactive shell, so that might lead to some files being unreadable and > that might potentially also lead to changed behaviour. > Actually systemd allows you to set a user and group you want for the > service, like e.g.: > > [Service] > User=root > Group=root > > > A don't remember what it sets by default. > (And certaily, root/root is generally not a safe practice, but just for > a test...) > > > Regards, > Nikolai > _______________________________________________ > fpc-devel maillist - fpc-devel@lists.freepascal.org > https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel >
_______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
