In rcmd(3) the environment variable RSH is used to indicate which program to execute in lieu of rsh itself. The code path present in rcmd(3) and rcmdsh() will result in continual execution of rsh if RSH is set to rsh itself. In fact, the RSH environment variable can only be safely set to a program that does not use rcmd(3). What possibly needs to happen here is for rcmd(3) to clear the RSH environment variable or otherwise make some effort to ensure that the program it is about to execute is not the same as the one that is currently executing. How-To-Repeat: export RSH=rsh rsh localhost who
For bugs matching the following conditions: - Status == In Progress - Assignee == "bugs@FreeBSD.org" - Last Modified Year <= 2017 Do - Set Status to "Open"
^Triage: the r* commands were removed 20171003.