Hello Harke,

Seth here. Um, are you trying to run a specific piece of software only or 
are you trying to run multiple pieces of software?

Seth

P.S. I know you have to make a file accessible at /etc/systemd/system/<your 
.service file here> w/ the proper instructions in that .service file. Now, 
to make it run should be easy, i.e. if this is just one piece of software. 

[Unit]
Description=More of what will happen!

[Service]
ExecStart= /your/path/to/the/.py/file.py

[Install]
WantedBy=multi-user.target

^
|
|

Try this!                                                                  
                                                                            
                                                                      

On Saturday, December 1, 2018 at 5:48:51 AM UTC-6, Harke Smits wrote:
>
> Hi Seth,
>
> In the meantime I think I tried just about any combination I can think of.
> Mostly I get the following error codes after demanding the status;
> Loaded....
> Active: failed 
> Process: 1002 ... code = exited, status=203/EXEC
> Main PID: 1002.....
>
> In short; no luck so far........
> I am doing something fundamentally wrong I think... Or it is just 
> impossible.
> I am lost here......
> Cheers,
> Harke
>
>
>
>
> On Fri, 30 Nov 2018 at 22:46, Mala Dies <[email protected] <javascript:>> 
> wrote:
>
>> Hello,
>>
>> When you type under [Service], use only the PATH. Try that idea first. I 
>> may be able to help out a bit.
>>
>> Seth
>>
>> P.S. For instance, say I have a Python file in this dir: 
>> /home/debian/LoveBone/. I would simply put, under the [Service] tag, 
>> ExecStart=/home/debain/LoveBone/MultipleIdeas.py for my PATH. Try that idea 
>> and think about moving that [Unit] option for Requires=graphical.target. 
>> Try that section under your [Install] section.
>>
>> On Friday, November 30, 2018 at 10:50:15 AM UTC-6, Harke Smits wrote:
>>>
>>> Hello Seth,
>>>
>>> Thanks a lot for your reaction. I already digested these pages (as good 
>>> as I could, I am an RF engineer, not a programmer). Unfortunately this does 
>>> not help me much. The service file is at the correct location.
>>> I hope to get some clue where I am doing something wrong.
>>> Thanks again, regards,
>>> Harke
>>>
>>>
>>> On Friday, 30 November 2018 12:18:26 UTC+1, Mala Dies wrote:
>>>>
>>>> Hello Again Harke,
>>>>
>>>> Seth here. You need to put your .service files in /etc/systemd/system/. 
>>>> I am pretty sure.
>>>>
>>>> Seth
>>>>
>>>> On Monday, November 26, 2018 at 5:49:16 AM UTC-6, Harke Smits wrote:
>>>>>
>>>>> Hello learned group,
>>>>>
>>>>> I have a Python application that I'd like to see start up on boot. It 
>>>>> uses Tkinter, so it needs the graphical environment. 
>>>>> Running: python /home/debian/eme/myprog.py from the QTerminal command 
>>>>> line works as expected. Not outside the LXQT environment, which is normal 
>>>>> I 
>>>>> think. 
>>>>> I made a service file: myprog.service like this:
>>>>> [Unit]
>>>>> Description=to invoke myprog automatically on boot
>>>>> Requires=graphical.target
>>>>> [Service]
>>>>> Type=simple
>>>>> WorkingDirectory=/home/debian/eme/
>>>>> ExecStart=python /home/debian/eme/myprog.py
>>>>> [Install]
>>>>> WantedBy=multi-user.target
>>>>>
>>>>> Service file is located at both: /etc/systemd/system/ and 
>>>>> /lib/systemd/system/ as I am unsure where it actually belongs. Of course 
>>>>> I 
>>>>> already spend a lot of time at internet to find a solution. Only succes 
>>>>> stories here....
>>>>> I entered the following;
>>>>> sudo systemctl enable myprog.service: nothing special
>>>>> sudo systemctl start myprog.service: service is not loaded 
>>>>> properly.....
>>>>> sudo systemctl status myprog.service: error (invalid argument), 
>>>>> inactive (dead).
>>>>>  
>>>>> Both from bash or within QTerminal: behaviour is the same.
>>>>>
>>>>> Please help me out what to do.
>>>>> Kind regards,
>>>>> Harke
>>>>>
>>>>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/beagleboard/goOORlttd2c/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/91cdcefd-06b6-4d68-96fe-a95b7dcd4573%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/beagleboard/91cdcefd-06b6-4d68-96fe-a95b7dcd4573%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/7ab54d0b-e341-48ff-89d6-d9fac79ec09a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to