install all progs in bindir?
Hi! In my opinion none of the rtmp* progs are really root-user-only, yet rtmpsrv/rtmpgw/rtmpsuck are installed in /usr/sbin instead of /usr/bin. Do you disagree with me on this? Just in case you do not, attached is a patch that makes them all install into /usr/bin. -- Anssi Hannula
Anssi Hannula wrote:
Hi!
In my opinion none of the rtmp* progs are really root-user-only, yet rtmpsrv/rtmpgw/rtmpsuck are installed in /usr/sbin instead of /usr/bin.
Do you disagree with me on this?
Obviously you need root privileges to set up the iptables or /etc/hosts redirects to use rtmpsrv/rtmpsuck. Your patch is wrong.
Howard Chu kirjoitti tiistai, 20. heinäkuuta 2010 00:53:02:
Anssi Hannula wrote:
Hi!
In my opinion none of the rtmp* progs are really root-user-only, yet rtmpsrv/rtmpgw/rtmpsuck are installed in /usr/sbin instead of /usr/bin.
Do you disagree with me on this?
Obviously you need root privileges to set up the iptables or /etc/hosts redirects to use rtmpsrv/rtmpsuck. Your patch is wrong.
But rtmpsuck does not seem to set that stuff itself, thus you can run it as non-root user after you've set up the necessary redirects yourself. For example, all X software is not in /usr/sbin even if you traditionally have to be root to setup and run X server. I don't intend to argue further, though, so feel free to leave it as you wish. -- Anssi Hannula
Your patch is wrong.
This is a great comment. So much arrogance in just a few words. I actually agree with Anssi. I have rtmpsuck running on a server in another country so I can watch RTMP streams that are Geo-blocked, without requiring a full-blown VPN. RTMPsuck doesn't need root privileges to run, and in my case, I don't need any IPTables rules. I think the patch is right. Howard, don't be a hater. The Internet is full of them already. cheers, Andy
Andy Botting wrote:
Your patch is wrong.
This is a great comment. So much arrogance in just a few words.
I actually agree with Anssi. I have rtmpsuck running on a server in another country so I can watch RTMP streams that are Geo-blocked, without requiring a full-blown VPN.
RTMPsuck doesn't need root privileges to run, and in my case, I don't need any IPTables rules. I think the patch is right.
And you're wrong too. rtmpgw/rtmpsrv/rtmpsuck are servers. Servers don't belong in /usr/bin.
Howard, don't be a hater. The Internet is full of them already.
Facts are what they are, there's neither love nor hate involved.
Howard Chu kirjoitti tiistai, 20. heinäkuuta 2010 20:30:32:
Andy Botting wrote:
I actually agree with Anssi. I have rtmpsuck running on a server in another country so I can watch RTMP streams that are Geo-blocked, without requiring a full-blown VPN.
RTMPsuck doesn't need root privileges to run, and in my case, I don't need any IPTables rules. I think the patch is right.
And you're wrong too.
rtmpgw/rtmpsrv/rtmpsuck are servers. Servers don't belong in /usr/bin.
Just out of interest, where's that rule from? At least Filesystem Hierarchy Standard doesn't mention servers, only "binaries used exclusively by the system administrator", which rtmp* AFAICS are not. -- Anssi Hannula
Anssi Hannula wrote:
Howard Chu kirjoitti tiistai, 20. heinäkuuta 2010 20:30:32:
Andy Botting wrote:
I actually agree with Anssi. I have rtmpsuck running on a server in another country so I can watch RTMP streams that are Geo-blocked, without requiring a full-blown VPN.
RTMPsuck doesn't need root privileges to run, and in my case, I don't need any IPTables rules. I think the patch is right.
And you're wrong too.
rtmpgw/rtmpsrv/rtmpsuck are servers. Servers don't belong in /usr/bin.
Just out of interest, where's that rule from?
Probably from the first Unix releases. Certainly it's true in my copy of the 4.2 BSD manuals.
At least Filesystem Hierarchy Standard doesn't mention servers, only "binaries used exclusively by the system administrator", which rtmp* AFAICS are not.
participants (3)
-
Andy Botting -
Anssi Hannula -
Howard Chu