From f3255d1e9f062e7783b05ab5b32ca70085170d79 Mon Sep 17 00:00:00 2001 From: Chris Hall Date: Wed, 30 Mar 2011 12:22:34 +0100 Subject: Better mechanism for handling depth_mark in vty->vio. Previous mechanism required special steps before any new output vty was opened -- which was easy to forget. New mechanism requires extra step when input and output are opened at the same time, which is less common, and more obviously requires the extra step. Fixes problem with "write memory" command. --- lib/vty_command.c | 9 --------- 1 file changed, 9 deletions(-) (limited to 'lib/vty_command.c') diff --git a/lib/vty_command.c b/lib/vty_command.c index 94ba6833..a63f6f0c 100644 --- a/lib/vty_command.c +++ b/lib/vty_command.c @@ -1154,15 +1154,6 @@ vty_cmd_reflect_line(vty vty) return ret ; } ; -/*------------------------------------------------------------------------------ - * Set the vio->depth_mark -- about to push vin and/or vout - */ -extern void -uty_cmd_depth_mark(vty_io vio) -{ - vio->depth_mark = vio->vin_depth ; -} - /*------------------------------------------------------------------------------ * Open the given file as an in pipe, if possible. * -- cgit v1.2.3