You are right Dennis. Excellent suggestions. Now I can get systemd to
work and can run my simple Python program and write file to memory using
stdout.
Now to get my GUI program to run. I think I may have clobbered something
in the Debian or Tkinter or something since my GUI program is giving me
a Tkinter error, the same one I had a couple of weeks ago and got past.
But it's reared its ugly head again. Very annoying. I suspect I have to
reload the Tkinter.
Ugly error:
_tkinter.TclError: no display name and no $DISPLAY environment variable
Thanks very much,
John
On 4/8/2016 5:11 AM, Dennis Lee Bieber wrote:
On Thu, 7 Apr 2016 21:18:43 -0700 (PDT), John Baker
<[email protected]> declaimed the
following:
ExecStart=/home/debian/Desktop/python SimB.py
The way I read that line says to run a Python interpreter located in
/home/debian/Desktop, passing it a file named SimB.py (located who knows
where).
I doubt you've installed a Python interpreter into your home directory.
I could see the line being:
ExecStart=python /home/debian/Desktop/SimB.py
to use the interpreter located on the regular search path (for something
starting as a service, likely the system Python).
Though one page found on Google mentions that systemd starts up with
fully "clean" environments -- so possibly not even the system search path
will be available and you need to provide both the path to the python
executable and the path to the script.
My other concern is: what do services use for stdout? Where would
anything from a print statement be sent? Maybe you need to provide output
redirection?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
