Timeline for Continuously listen to tcp port via terminal
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 13, 2018 at 14:57 | comment | added | Scott Prive | I would emphasize: just run this as the root user and have it check if real UID is 0. Alternatively, run it as a user with sudo configured as NOPASSWD ALL. Two choices. You won't get far automating things if there's a prompt to deal with. (Don't try what some recommend, trying to "answer" the password prompt, ugh) | |
| Mar 10, 2016 at 12:34 | vote | accept | S4M11R | ||
| Mar 7, 2016 at 11:24 | comment | added | dreamlax | Yeah, that would be better I think! | |
| Mar 7, 2016 at 10:43 | history | edited | S4M11R | CC BY-SA 3.0 |
deleted 5 characters in body
|
| Mar 7, 2016 at 10:30 | history | edited | S4M11R | CC BY-SA 3.0 |
added 209 characters in body
|
| Mar 7, 2016 at 10:26 | comment | added | S4M11R | Better to remove sudo from script then run script as sudo? Ex: sudo tcpListen.sh | |
| Mar 7, 2016 at 10:21 | comment | added | dreamlax |
I would avoid putting sudo in the loop like that ... unless it is configured not to prompt for a password, it may cause issues if nothing is received for 15 minutes (or whatever the sudo timeout is configured on your system) and sudo is run again.
|
|
| Mar 7, 2016 at 10:20 | history | answered | S4M11R | CC BY-SA 3.0 |