Claudio Jeker <cje...@diehard.n-r-g.com> wrote: > On Wed, Jul 29, 2020 at 04:43:18PM +0200, Klemens Nanni wrote: > > On Wed, Jul 29, 2020 at 05:33:14PM +0300, Kapetanakis Giannis wrote: > > > Wouldn't this break those who already have > > > !route -T2 > > > > > > in their hostname.if files? > > No, > > > > $ route -T1 exec id -R > > 1 > > $ route -T0 exec route -T1 exec id -R > > 1 > > But: > $ route -T2 exec id -R > 2 > $ route -T2 exec route -T0 exec id -R > route: setrtable: Operation not permitted > > Only root can change the rdomain if it is currently != 0.
That worry was stated in my email, but not so accurately, thank you. So now you can't make a rdomain-0 !command in the global scope. And if we start playing with "early !commands run in 0", that gets even more messy.
