The other options besides "in" include "LINE" or "what should we put in the syslog as to why the reload is occurring". This means it will pick up anything that isn't already a keyword (for example "in" provides an option, "int" is a reason).
If we fix the behavior what does the fix look like? Do we not allow any reason that starts with "i"(in) "c" (cancel) or "a"(at)? But then what if you want a reload reason of "reload installing new software"? Should this be blocked? On Mon, Oct 7, 2013 at 6:56 AM, Luis Miguel Cruz Miranda <luis...@imasd.net>wrote: > Hi all, > > I am not sure if this this an IOS version related issue. > The issue is... > - "reload in X" schedules a reload in X minutes (that is the correct > behaviour) > - "reload intasdajxjxhaajsa X" just goes ahead with an inmediate reload, > it is the same as "reload" command. > > It shouldn't be a problem since there are some confirmations but... I > just did "reload int 10" and pushed enter few times thinking the command > was right... :-( imagine... > > Saw in... > c3825-spservicesk9-mz.124-24.T5.bin > c2600-advsecurityk9-mz.124-15.T13.bin > > Does anyone know if this was fixed or the expected behaviour? > I think IOS CLI should complain about it as it does with other commands. > > Luis > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
