My bad. After hours of debugging, I figured it out. One of our plugin unformat function was checking for end-of-input, which was not the case when using "exec" command. Indeed, "exec" reads each line of the parsed file and put them next to each other in the (input) buffer. That's why it was silently denying those commands.
Justin > Hi everyone, > > Just noticed that my file was not executed with "vppctl exec <file>". > Actually, > it *is* executed, as long as a line doesn't contain a command for my plugin. > Is > "exec" only for some vpp "core" commands, such as "set" ? I already tried the > alternative solution by calling "vppctl <command>" for each command, but that > leads to a vpp crash when too much commands are involved (around 10000 > commands). That's why I thought about the "exec" solution that seems cleaner. > > Any idea ? Any other solution ? Thanks ! > > Justin _______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
