Skip to content

Instantly share code, notes, and snippets.

@frojnd

frojnd/gist:d790000c9bbed3252fe8cef64d8f7397

Created April 3, 2020 12:31
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save frojnd/d790000c9bbed3252fe8cef64d8f7397 to your computer and use it in GitHub Desktop.
Save frojnd/d790000c9bbed3252fe8cef64d8f7397 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
gistfile1.txt
$ sudo systemctl status tty-observer.service
● tty-observer.service - "Script looks for ttys and starts picocom for each tty"
Loaded: loaded (/etc/systemd/system/tty-observer.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2020-04-03 14:30:40 CEST; 6s ago
Process: 919 ExecStart=/usr/bin/screen -S picocom -d -m /usr/bin/start_picocom.sh (code=exited, status=0/SUCCESS)
Main PID: 920 (screen)
Tasks: 3 (limit: 4915)
Memory: 2.1M
CGroup: /system.slice/tty-observer.service
├─920 /usr/bin/SCREEN -S picocom -d -m /usr/bin/start_picocom.sh
├─921 /bin/bash /usr/bin/start_picocom.sh
└─930 picocom -b 115200 -l /dev/ttyUSB0 --logfile /logs/picocomttyUSB0.log
Apr 03 14:30:40 debian systemd[1]: Starting "Script looks for ttys and starts picocom for each tty"...
Apr 03 14:30:40 debian systemd[1]: Started "Script looks for ttys and starts picocom for each tty".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment