search

BradleyA / pi-display

Displays are Pimoroni Blinkt, Scroll-pHAT, and Scroll-pHAT-HD connected to Raspberry Pi 3 using Triple GPIO Multiplexing Expansion Board
MIT License
3 stars 0 forks source link

add pi-display/main/test2/display-led.py to crontab #17

Closed BradleyA closed 6 years ago

BradleyA commented 6 years ago

pi-display/main/test2/display-led.py display on blinkt => notes < check if VISUAL is set to editor env | grep -i visual source ~/.bashrc

sudo vi /etc/cron.allow add user name approved to add to crontab uadmin

crontab -e

add line below to file /2 * /usr/local/bin/display-led.py >> /tmp/crontab-test-log-file 2>&1

BradleyA commented 6 years ago

102225 uadmin@six-rpi3b:~ crontab -l

. . .
@reboot /usr/local/bin/larson-1.py >> /tmp/crontab-test-log-file 2>&1
*/2 * * * * sleep 30 && /usr/local/bin/display-led.py >> /tmp/crontab-test-log-file 2>&1
@reboot /usr/local/bin/plasma-1.py >> /tmp/crontab-test-log-file 2>&1
#   @reboot sleep 30 && /usr/local/bin/display-message-hd.py >> /tmp/crontab-test-log-file 2>&1
*/2 * * * * sleep 30 && /usr/local/bin/create-message.sh us-tx-cluster-1 uadmin >> /tmp/crontab-test-log-file 2>&1
BradleyA commented 6 years ago

102230 uadmin@two-rpi3b:~ crontab -l

. . .
@reboot /usr/local/bin/larson-1.py >> /tmp/crontab-test-log-file 2>&1
*/2 * * * * sleep 30 && /usr/local/bin/display-led.py >> /tmp/crontab-test-log-file 2>&1
@reboot sleep 30 && /usr/local/bin/display-message.py >> /tmp/crontab-test-message-log-file 2>&1
BradleyA commented 6 years ago

102232 uadmin@three-rpi3b:~ crontab -l

. . . 
reboot /usr/local/bin/larson-1.py >> /tmp/crontab-test-log-file 2>&1
*/2 * * * * sleep 30 && /usr/local/bin/display-led.py >> /tmp/crontab-test-log-file 2>&1
@reboot sleep 30 && /usr/local/bin/display-message.py >> /tmp/crontab-test-message-log-file 2>&1
BradleyA commented 6 years ago

Done.

Thinking about moving the services to containers (Thinking not just off the top of my head; the container will create an security risk because of the need for --privileged) or systemd. (systemctl status docker.service ; journalctl -xe )

Full container capabilities (--privileged)

The --privileged flag gives all capabilities to the container, and it also lifts all the limitations enforced by the device cgroup controller. In other words, the container can then do almost everything that the host can do. This flag exists to allow special use-cases, like running Docker within Docker.