You realize you're responding to a post that is nearly a year old ? On Christmas of all days . . .
Merry Christmas, and go sit down and relax with the family . . . On Fri, Dec 25, 2015 at 3:30 PM, Bit Pusher <[email protected]> wrote: > The output of stderr error can be found using "sudo systemctl status > SERVICE_NAME.service"; I'm not sure where stdout is going (perhaps > /dev/null?). Irrespective, when doing systemd development, I always "tee" > both stdout and stderr into a log file under my home directory. By using > tee, I see the stdout when running with a debugger, and it is also logged > when running at startup. Since I have standardized on using python for all > scripts (whenever possible), this is relatively simple using the imported > sys module (I can post if there is interest and someone can explain simply > how to include code in a post). > > > On Monday, January 12, 2015 at 6:36:35 PM UTC-5, Devin Linnington wrote: >> >> I'm running debian on my BBB (2014-05-14), and I noticed that you guys >> are using systemd so when I made my new server app I'm using systemd. >> Here's my server file, pretty simple: >> >> [Unit] >> Description=CS XMLRPC Server >> Requires=network.target >> After=network.target >> >> [Service] >> ExecStart=/usr/local/bin/cs_xmlrpc 8888 >> >> [Install] >> WantedBy=multi-user.target >> >> >> I can start/stop it fine, however I can't seem to find where the >> stdout/stderr from the program is going. I've checked /var/log/syslog, >> /var/log/messages, dmesg, and systemd-journalctl. None of them seem to >> contain the output from my program. I've read everywhere that it's either >> syslog or journalctl, so I don't know where else to look. >> >> Any ideas? Should I use one of the debian testing snapshots instead? >> >> Thanks, >> -Devin >> > -- > 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. > -- 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.
