Exec node with sudo rights?

[bad...@gmail.com]

Hi,

I'm interacting with sensors on a Raspberry Pi via a Python script, which requires sudo rights. The data gets into Node-RED via UDP. The hardware seems to have occasional hick ups, and the script stalls. This triggers an event in Node-RED, but now I'm stuck: Manually, I issue 'sudo killall python' and 'sudo python sensors.py' - but can I do this automatically from within my flow?

Any hints much appreciated!

Boris

[Dave C-J]

Hi,

well several dodgy options... so read around each first...

1) run Node-RED as root....

2) https://ubuntuforums.org/showthread.php?t=791719

3) http://www.tuxation.com/setuid-on-shell-scripts.html

4) re-write the sensor code in Node-RED also ;-)

Boris

--
http://nodered.org
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
regards

Dave Conway-Jones

[li...@amcc.myzen.co.uk]

Hi Boris,

You might be able to avoid the need to run the python script as root (depending on what it's trying to do) by adding the logged in user to some extra groups.

e.g. to read /dev/ttyUSB* files

sudo adduser boris dialout

or to access gpio and/or spi on Raspberry Pi

sudo adduser boris gpio spi

You need to logout and login again before it takes effect.

To see which groups you're in type

groups

Regards,
Aideen

[bad...@gmail.com]

I love the way CJ calls them "dodgy options", because that's exactly how I feel about them. Aideen's suggestion is on my try-out list for tonight. I'm going to avoid the 'killall' step by rebooting the Pi into Node-RED and let the exec node take care of starting the Python command.

All part of the big "Node-RED interoperability with data silos" review.

Boris

[chris mobberley]

I have to say I am one of those using the run node-red as sudo dodgy workers. I had so many headaches with trying to work with a very similar situation to yourself. I set up a new user and group to run node-red under and I ended up elevating the rights so much I may as well have just stuck with sudo. Granted my linux skills are dire..as are most of my skills come to think of it, so there may be another fix but it didn't warrant me losing hours of my life to just for the sake of running sudo. I'm sure "hackers" care more about other stuff than my raspberry pi home server..

[Dave C-J]

Chris,

just because I said it's dodgy and advise against doing it... doesn't mean I don't ;-) - just be aware of the risks.

--

http://nodered.org
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
regards

Dave Conway-Jones

[Peter Scargill]

Adding users to the gpio group is good for Raspberry Pi but no good for many other similar boards that don't have that group.

[Peter Scargill]

There is no gpio group – only have that on a Raspberry Pi.

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to a topic in the Google Groups "Node-RED" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/node-red/82-KeIfIIoU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to node-red+u...@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.