When attempting to switch runtime permissions over to
the correct group specified for the vty group, if the
user specified to run as does not have that vty group
then do warn about the issue and stop running
Signed-off-by: Donald Sharp
Reported-by: Thomas Martin
On 4/8/2016 10:22 AM, Donald Sharp wrote:
Jafar -
You know that, I know that. End Users are going to see the
incongruence and start asking questions. If I can stop a question
from being asked. I think that is a win.
I don't disagree with you on this one. Maybe we should just change how
Jafar -
You know that, I know that. End Users are going to see the incongruence
and start asking questions. If I can stop a question from being asked. I
think that is a win.
On Fri, Apr 8, 2016 at 11:11 AM, Jafar Al-Gharaibeh
wrote:
>
> On 4/8/2016 7:24 AM, Donald Sharp
On 04/08/2016 12:11 PM, Jafar Al-Gharaibeh wrote:
> On 4/8/2016 7:24 AM, Donald Sharp wrote:
>> We never start at an initial Link up. Possible to get another patch
>> to fix that issue?
>
> The way I read this patch (and according to Christian's comment ) is
> to monitor if the
> interface
On 4/8/2016 7:24 AM, Donald Sharp wrote:
Christian -
If I start Quagga, after the link is already brought up:
dell-s6000-02# show int swp31s2.4
Interface swp31s2.4 is up, line protocol is up
Link ups: 0last: (never)
Link downs: 0last: (never)
PTM status: disabled
Christian -
If I start Quagga, after the link is already brought up:
dell-s6000-02# show int swp31s2.4
Interface swp31s2.4 is up, line protocol is up
Link ups: 0last: (never)
Link downs: 0last: (never)
PTM status: disabled
vrf: vrf1014
index 58 metric 0 mtu 1500