1999-10-29 20:10:10 +08:00
|
|
|
/*
|
|
|
|
* BIRD Internet Routing Daemon -- Command-Line Interface
|
|
|
|
*
|
2000-06-03 22:40:39 +08:00
|
|
|
* (c) 1999--2000 Martin Mares <mj@ucw.cz>
|
1999-10-29 20:10:10 +08:00
|
|
|
*
|
|
|
|
* Can be freely distributed and used under the terms of the GNU GPL.
|
|
|
|
*/
|
|
|
|
|
2000-06-03 22:40:39 +08:00
|
|
|
/**
|
|
|
|
* DOC: Command line interface
|
|
|
|
*
|
|
|
|
* This module takes care of the BIRD's command-line interface (CLI).
|
|
|
|
* The CLI exists to provide a way to control BIRD remotely and to inspect
|
|
|
|
* its status. It uses a very simple textual protocol over a stream
|
|
|
|
* connection provided by the platform dependent code (on UNIX systems,
|
|
|
|
* it's a UNIX domain socket).
|
|
|
|
*
|
|
|
|
* Each session of the CLI consists of a sequence of request and replies,
|
|
|
|
* slightly resembling the FTP and SMTP protocols.
|
|
|
|
* Requests are commands encoded as a single line of text, replies are
|
|
|
|
* sequences of lines starting with a four-digit code followed by either
|
|
|
|
* a space (if it's the last line of the reply) or a minus sign (when the
|
|
|
|
* reply is going to continue with the next line), the rest of the line
|
|
|
|
* contains a textual message semantics of which depends on the numeric
|
|
|
|
* code. If a reply line has the same code as the previous one and it's
|
|
|
|
* a continuation line, the whole prefix can be replaced by a single
|
|
|
|
* white space character.
|
|
|
|
*
|
2000-06-07 21:25:53 +08:00
|
|
|
* Reply codes starting with 0 stand for `action successfully completed' messages,
|
2000-06-03 22:40:39 +08:00
|
|
|
* 1 means `table entry', 8 `runtime error' and 9 `syntax error'.
|
|
|
|
*
|
|
|
|
* Each CLI session is internally represented by a &cli structure and a
|
|
|
|
* resource pool containing all resources associated with the connection,
|
2000-06-07 21:25:53 +08:00
|
|
|
* so that it can be easily freed whenever the connection gets closed, not depending
|
2000-06-03 22:40:39 +08:00
|
|
|
* on the current state of command processing.
|
|
|
|
*
|
|
|
|
* The CLI commands are declared as a part of the configuration grammar
|
2000-06-08 20:37:21 +08:00
|
|
|
* by using the |CF_CLI| macro. When a command is received, it is processed
|
2000-06-07 20:29:08 +08:00
|
|
|
* by the same lexical analyzer and parser as used for the configuration, but
|
2000-06-03 22:40:39 +08:00
|
|
|
* it's switched to a special mode by prepending a fake token to the text,
|
|
|
|
* so that it uses only the CLI command rules. Then the parser invokes
|
|
|
|
* an execution routine corresponding to the command, which either constructs
|
2000-06-08 20:37:21 +08:00
|
|
|
* the whole reply and returns it back or (in case it expects the reply will be long)
|
2000-06-03 22:40:39 +08:00
|
|
|
* it prints a partial reply and asks the CLI module (using the @cont hook)
|
2000-06-07 21:25:53 +08:00
|
|
|
* to call it again when the output is transferred to the user.
|
2000-06-03 22:40:39 +08:00
|
|
|
*
|
|
|
|
* The @this_cli variable points to a &cli structure of the session being
|
|
|
|
* currently parsed, but it's of course available only in command handlers
|
|
|
|
* not entered using the @cont hook.
|
2009-07-14 20:18:54 +08:00
|
|
|
*
|
|
|
|
* TX buffer management works as follows: At cli.tx_buf there is a
|
|
|
|
* list of TX buffers (struct cli_out), cli.tx_write is the buffer
|
|
|
|
* currently used by the producer (cli_printf(), cli_alloc_out()) and
|
|
|
|
* cli.tx_pos is the buffer currently used by the consumer
|
|
|
|
* (cli_write(), in system dependent code). The producer uses
|
|
|
|
* cli_out.wpos ptr as the current write position and the consumer
|
|
|
|
* uses cli_out.outpos ptr as the current read position. When the
|
|
|
|
* producer produces something, it calls cli_write_trigger(). If there
|
|
|
|
* is not enough space in the current buffer, the producer allocates
|
|
|
|
* the new one. When the consumer processes everything in the buffer
|
|
|
|
* queue, it calls cli_written(), tha frees all buffers (except the
|
|
|
|
* first one) and schedules cli.event .
|
|
|
|
*
|
2000-06-03 22:40:39 +08:00
|
|
|
*/
|
|
|
|
|
1999-10-29 20:10:10 +08:00
|
|
|
#include "nest/bird.h"
|
|
|
|
#include "nest/cli.h"
|
Parse CLI commands. We use the same parser as for configuration files (because
we want to allow filter and similar complex constructs to be used in commands
and we should avoid code duplication), only with CLI_MARKER token prepended
before the whole input.
Defined macro CF_CLI(cmd, args, help) for defining CLI commands in .Y files.
The first argument specifies the command itself, the remaining two arguments
are copied to the help file (er, will be copied after the help file starts
to exist). This macro automatically creates a skeleton rule for the command,
you only need to append arguments as in:
CF_CLI(STEAL MONEY, <$>, [[Steal <$> US dollars or equivalent in any other currency]]): NUM {
cli_msg(0, "%d$ stolen", $3);
} ;
Also don't forget to reset lexer state between inputs.
1999-11-01 01:47:47 +08:00
|
|
|
#include "conf/conf.h"
|
|
|
|
#include "lib/string.h"
|
1999-10-29 20:10:10 +08:00
|
|
|
|
|
|
|
pool *cli_pool;
|
|
|
|
|
1999-12-06 20:34:45 +08:00
|
|
|
static byte *
|
|
|
|
cli_alloc_out(cli *c, int size)
|
|
|
|
{
|
|
|
|
struct cli_out *o;
|
|
|
|
|
|
|
|
if (!(o = c->tx_write) || o->wpos + size > o->end)
|
|
|
|
{
|
|
|
|
if (!o && c->tx_buf)
|
|
|
|
o = c->tx_buf;
|
|
|
|
else
|
|
|
|
{
|
|
|
|
o = mb_alloc(c->pool, sizeof(struct cli_out) + CLI_TX_BUF_SIZE);
|
|
|
|
if (c->tx_write)
|
|
|
|
c->tx_write->next = o;
|
|
|
|
else
|
|
|
|
c->tx_buf = o;
|
|
|
|
o->wpos = o->outpos = o->buf;
|
|
|
|
o->end = o->buf + CLI_TX_BUF_SIZE;
|
|
|
|
}
|
|
|
|
c->tx_write = o;
|
|
|
|
if (!c->tx_pos)
|
|
|
|
c->tx_pos = o;
|
2000-04-28 06:35:08 +08:00
|
|
|
o->next = NULL;
|
1999-12-06 20:34:45 +08:00
|
|
|
}
|
|
|
|
o->wpos += size;
|
|
|
|
return o->wpos - size;
|
|
|
|
}
|
|
|
|
|
2000-06-03 22:40:39 +08:00
|
|
|
/**
|
|
|
|
* cli_printf - send reply to a CLI connection
|
|
|
|
* @c: CLI connection
|
|
|
|
* @code: numeric code of the reply, negative for continuation lines
|
|
|
|
* @msg: a printf()-like formatting string.
|
|
|
|
*
|
|
|
|
* This function send a single line of reply to a given CLI connection.
|
|
|
|
* In works in all aspects like bsprintf() except that it automatically
|
|
|
|
* prepends the reply line prefix.
|
|
|
|
*
|
|
|
|
* Please note that if the connection can be already busy sending some
|
|
|
|
* data in which case cli_printf() stores the output to a temporary buffer,
|
|
|
|
* so please avoid sending a large batch of replies without waiting
|
|
|
|
* for the buffers to be flushed.
|
|
|
|
*
|
|
|
|
* If you want to write to the current CLI output, you can use the cli_msg()
|
|
|
|
* macro instead.
|
|
|
|
*/
|
1999-10-29 20:10:10 +08:00
|
|
|
void
|
|
|
|
cli_printf(cli *c, int code, char *msg, ...)
|
|
|
|
{
|
|
|
|
va_list args;
|
2011-07-04 01:43:30 +08:00
|
|
|
byte buf[CLI_LINE_SIZE];
|
1999-10-31 23:43:44 +08:00
|
|
|
int cd = code;
|
|
|
|
int size, cnt;
|
1999-10-29 20:10:10 +08:00
|
|
|
|
1999-10-31 23:43:44 +08:00
|
|
|
if (cd < 0)
|
|
|
|
{
|
|
|
|
cd = -cd;
|
|
|
|
if (cd == c->last_reply)
|
|
|
|
size = bsprintf(buf, " ");
|
|
|
|
else
|
|
|
|
size = bsprintf(buf, "%04d-", cd);
|
|
|
|
}
|
1999-10-29 20:10:10 +08:00
|
|
|
else
|
1999-10-31 23:43:44 +08:00
|
|
|
size = bsprintf(buf, "%04d ", cd);
|
|
|
|
c->last_reply = cd;
|
2004-06-01 02:08:50 +08:00
|
|
|
va_start(args, msg);
|
1999-10-31 23:43:44 +08:00
|
|
|
cnt = bvsnprintf(buf+size, sizeof(buf)-size-1, msg, args);
|
2004-06-01 02:08:50 +08:00
|
|
|
va_end(args);
|
1999-10-31 23:43:44 +08:00
|
|
|
if (cnt < 0)
|
|
|
|
{
|
|
|
|
cli_printf(c, code < 0 ? -8000 : 8000, "<line overflow>");
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
size += cnt;
|
1999-10-29 20:10:10 +08:00
|
|
|
buf[size++] = '\n';
|
1999-12-06 20:34:45 +08:00
|
|
|
memcpy(cli_alloc_out(c, size), buf, size);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
cli_copy_message(cli *c)
|
|
|
|
{
|
|
|
|
byte *p, *q;
|
|
|
|
unsigned int cnt = 2;
|
|
|
|
|
|
|
|
if (c->ring_overflow)
|
1999-10-29 20:10:10 +08:00
|
|
|
{
|
1999-12-06 20:34:45 +08:00
|
|
|
byte buf[64];
|
|
|
|
int n = bsprintf(buf, "<%d messages lost>\n", c->ring_overflow);
|
|
|
|
c->ring_overflow = 0;
|
|
|
|
memcpy(cli_alloc_out(c, n), buf, n);
|
1999-10-29 20:10:10 +08:00
|
|
|
}
|
1999-12-06 20:34:45 +08:00
|
|
|
p = c->ring_read;
|
|
|
|
while (*p)
|
|
|
|
{
|
|
|
|
cnt++;
|
|
|
|
p++;
|
|
|
|
if (p == c->ring_end)
|
|
|
|
p = c->ring_buf;
|
|
|
|
ASSERT(p != c->ring_write);
|
|
|
|
}
|
|
|
|
c->async_msg_size += cnt;
|
|
|
|
q = cli_alloc_out(c, cnt);
|
|
|
|
*q++ = '+';
|
|
|
|
p = c->ring_read;
|
|
|
|
do
|
|
|
|
{
|
|
|
|
*q = *p++;
|
|
|
|
if (p == c->ring_end)
|
|
|
|
p = c->ring_buf;
|
|
|
|
}
|
|
|
|
while (*q++);
|
|
|
|
c->ring_read = p;
|
|
|
|
q[-1] = '\n';
|
1999-10-29 20:10:10 +08:00
|
|
|
}
|
|
|
|
|
1999-10-31 23:43:44 +08:00
|
|
|
static void
|
|
|
|
cli_hello(cli *c)
|
|
|
|
{
|
|
|
|
cli_printf(c, 1, "BIRD " BIRD_VERSION " ready.");
|
|
|
|
c->cont = NULL;
|
|
|
|
}
|
|
|
|
|
1999-10-29 20:10:10 +08:00
|
|
|
static void
|
|
|
|
cli_free_out(cli *c)
|
|
|
|
{
|
|
|
|
struct cli_out *o, *p;
|
|
|
|
|
|
|
|
if (o = c->tx_buf)
|
|
|
|
{
|
|
|
|
o->wpos = o->outpos = o->buf;
|
|
|
|
while (p = o->next)
|
|
|
|
{
|
|
|
|
o->next = p->next;
|
|
|
|
mb_free(p);
|
|
|
|
}
|
|
|
|
}
|
2000-04-28 06:35:08 +08:00
|
|
|
c->tx_write = c->tx_pos = NULL;
|
1999-12-06 20:34:45 +08:00
|
|
|
c->async_msg_size = 0;
|
1999-10-29 20:10:10 +08:00
|
|
|
}
|
|
|
|
|
2009-07-14 20:18:54 +08:00
|
|
|
void
|
|
|
|
cli_written(cli *c)
|
|
|
|
{
|
|
|
|
cli_free_out(c);
|
|
|
|
ev_schedule(c->event);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
Parse CLI commands. We use the same parser as for configuration files (because
we want to allow filter and similar complex constructs to be used in commands
and we should avoid code duplication), only with CLI_MARKER token prepended
before the whole input.
Defined macro CF_CLI(cmd, args, help) for defining CLI commands in .Y files.
The first argument specifies the command itself, the remaining two arguments
are copied to the help file (er, will be copied after the help file starts
to exist). This macro automatically creates a skeleton rule for the command,
you only need to append arguments as in:
CF_CLI(STEAL MONEY, <$>, [[Steal <$> US dollars or equivalent in any other currency]]): NUM {
cli_msg(0, "%d$ stolen", $3);
} ;
Also don't forget to reset lexer state between inputs.
1999-11-01 01:47:47 +08:00
|
|
|
static byte *cli_rh_pos;
|
|
|
|
static unsigned int cli_rh_len;
|
|
|
|
static int cli_rh_trick_flag;
|
|
|
|
struct cli *this_cli;
|
|
|
|
|
|
|
|
static int
|
|
|
|
cli_cmd_read_hook(byte *buf, unsigned int max)
|
|
|
|
{
|
|
|
|
if (!cli_rh_trick_flag)
|
|
|
|
{
|
|
|
|
cli_rh_trick_flag = 1;
|
|
|
|
buf[0] = '!';
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
if (max > cli_rh_len)
|
|
|
|
max = cli_rh_len;
|
|
|
|
memcpy(buf, cli_rh_pos, max);
|
|
|
|
cli_rh_pos += max;
|
|
|
|
cli_rh_len -= max;
|
|
|
|
return max;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
cli_command(struct cli *c)
|
|
|
|
{
|
|
|
|
struct config f;
|
|
|
|
int res;
|
|
|
|
|
2000-05-30 06:10:18 +08:00
|
|
|
if (config->cli_debug > 1)
|
|
|
|
log(L_TRACE "CLI: %s", c->rx_buf);
|
1999-11-30 22:04:09 +08:00
|
|
|
bzero(&f, sizeof(f));
|
Parse CLI commands. We use the same parser as for configuration files (because
we want to allow filter and similar complex constructs to be used in commands
and we should avoid code duplication), only with CLI_MARKER token prepended
before the whole input.
Defined macro CF_CLI(cmd, args, help) for defining CLI commands in .Y files.
The first argument specifies the command itself, the remaining two arguments
are copied to the help file (er, will be copied after the help file starts
to exist). This macro automatically creates a skeleton rule for the command,
you only need to append arguments as in:
CF_CLI(STEAL MONEY, <$>, [[Steal <$> US dollars or equivalent in any other currency]]): NUM {
cli_msg(0, "%d$ stolen", $3);
} ;
Also don't forget to reset lexer state between inputs.
1999-11-01 01:47:47 +08:00
|
|
|
f.mem = c->parser_pool;
|
|
|
|
cf_read_hook = cli_cmd_read_hook;
|
2011-09-12 03:21:47 +08:00
|
|
|
cf_open_hook = NULL;
|
Parse CLI commands. We use the same parser as for configuration files (because
we want to allow filter and similar complex constructs to be used in commands
and we should avoid code duplication), only with CLI_MARKER token prepended
before the whole input.
Defined macro CF_CLI(cmd, args, help) for defining CLI commands in .Y files.
The first argument specifies the command itself, the remaining two arguments
are copied to the help file (er, will be copied after the help file starts
to exist). This macro automatically creates a skeleton rule for the command,
you only need to append arguments as in:
CF_CLI(STEAL MONEY, <$>, [[Steal <$> US dollars or equivalent in any other currency]]): NUM {
cli_msg(0, "%d$ stolen", $3);
} ;
Also don't forget to reset lexer state between inputs.
1999-11-01 01:47:47 +08:00
|
|
|
cli_rh_pos = c->rx_buf;
|
|
|
|
cli_rh_len = strlen(c->rx_buf);
|
|
|
|
cli_rh_trick_flag = 0;
|
|
|
|
this_cli = c;
|
|
|
|
lp_flush(c->parser_pool);
|
1999-12-01 23:07:56 +08:00
|
|
|
res = cli_parse(&f);
|
Parse CLI commands. We use the same parser as for configuration files (because
we want to allow filter and similar complex constructs to be used in commands
and we should avoid code duplication), only with CLI_MARKER token prepended
before the whole input.
Defined macro CF_CLI(cmd, args, help) for defining CLI commands in .Y files.
The first argument specifies the command itself, the remaining two arguments
are copied to the help file (er, will be copied after the help file starts
to exist). This macro automatically creates a skeleton rule for the command,
you only need to append arguments as in:
CF_CLI(STEAL MONEY, <$>, [[Steal <$> US dollars or equivalent in any other currency]]): NUM {
cli_msg(0, "%d$ stolen", $3);
} ;
Also don't forget to reset lexer state between inputs.
1999-11-01 01:47:47 +08:00
|
|
|
if (!res)
|
|
|
|
cli_printf(c, 9001, f.err_msg);
|
|
|
|
}
|
|
|
|
|
2000-04-28 06:35:08 +08:00
|
|
|
static void
|
1999-10-29 20:10:10 +08:00
|
|
|
cli_event(void *data)
|
|
|
|
{
|
|
|
|
cli *c = data;
|
|
|
|
int err;
|
|
|
|
|
1999-12-06 20:34:45 +08:00
|
|
|
while (c->ring_read != c->ring_write &&
|
|
|
|
c->async_msg_size < CLI_MAX_ASYNC_QUEUE)
|
|
|
|
cli_copy_message(c);
|
|
|
|
|
1999-10-31 23:43:44 +08:00
|
|
|
if (c->tx_pos)
|
|
|
|
;
|
|
|
|
else if (c->cont)
|
|
|
|
c->cont(c);
|
|
|
|
else
|
1999-10-29 20:10:10 +08:00
|
|
|
{
|
1999-10-31 23:43:44 +08:00
|
|
|
err = cli_get_command(c);
|
|
|
|
if (!err)
|
2000-04-28 06:35:08 +08:00
|
|
|
return;
|
1999-10-31 23:43:44 +08:00
|
|
|
if (err < 0)
|
|
|
|
cli_printf(c, 9000, "Command too long");
|
|
|
|
else
|
Parse CLI commands. We use the same parser as for configuration files (because
we want to allow filter and similar complex constructs to be used in commands
and we should avoid code duplication), only with CLI_MARKER token prepended
before the whole input.
Defined macro CF_CLI(cmd, args, help) for defining CLI commands in .Y files.
The first argument specifies the command itself, the remaining two arguments
are copied to the help file (er, will be copied after the help file starts
to exist). This macro automatically creates a skeleton rule for the command,
you only need to append arguments as in:
CF_CLI(STEAL MONEY, <$>, [[Steal <$> US dollars or equivalent in any other currency]]): NUM {
cli_msg(0, "%d$ stolen", $3);
} ;
Also don't forget to reset lexer state between inputs.
1999-11-01 01:47:47 +08:00
|
|
|
cli_command(c);
|
1999-10-29 20:10:10 +08:00
|
|
|
}
|
2009-07-14 20:18:54 +08:00
|
|
|
|
|
|
|
cli_write_trigger(c);
|
1999-10-29 20:10:10 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
cli *
|
|
|
|
cli_new(void *priv)
|
|
|
|
{
|
|
|
|
pool *p = rp_new(cli_pool, "CLI");
|
|
|
|
cli *c = mb_alloc(p, sizeof(cli));
|
|
|
|
|
1999-12-06 20:34:45 +08:00
|
|
|
bzero(c, sizeof(cli));
|
1999-10-29 20:10:10 +08:00
|
|
|
c->pool = p;
|
|
|
|
c->priv = priv;
|
|
|
|
c->event = ev_new(p);
|
|
|
|
c->event->hook = cli_event;
|
|
|
|
c->event->data = c;
|
1999-10-31 23:43:44 +08:00
|
|
|
c->cont = cli_hello;
|
Parse CLI commands. We use the same parser as for configuration files (because
we want to allow filter and similar complex constructs to be used in commands
and we should avoid code duplication), only with CLI_MARKER token prepended
before the whole input.
Defined macro CF_CLI(cmd, args, help) for defining CLI commands in .Y files.
The first argument specifies the command itself, the remaining two arguments
are copied to the help file (er, will be copied after the help file starts
to exist). This macro automatically creates a skeleton rule for the command,
you only need to append arguments as in:
CF_CLI(STEAL MONEY, <$>, [[Steal <$> US dollars or equivalent in any other currency]]): NUM {
cli_msg(0, "%d$ stolen", $3);
} ;
Also don't forget to reset lexer state between inputs.
1999-11-01 01:47:47 +08:00
|
|
|
c->parser_pool = lp_new(c->pool, 4096);
|
1999-12-06 20:34:45 +08:00
|
|
|
c->rx_buf = mb_alloc(c->pool, CLI_RX_BUF_SIZE);
|
1999-10-31 23:43:44 +08:00
|
|
|
ev_schedule(c->event);
|
1999-10-29 20:10:10 +08:00
|
|
|
return c;
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
cli_kick(cli *c)
|
|
|
|
{
|
1999-10-31 23:43:44 +08:00
|
|
|
if (!c->cont && !c->tx_pos)
|
|
|
|
ev_schedule(c->event);
|
1999-10-29 20:10:10 +08:00
|
|
|
}
|
|
|
|
|
1999-12-06 20:34:45 +08:00
|
|
|
static list cli_log_hooks;
|
|
|
|
static int cli_log_inited;
|
|
|
|
|
|
|
|
void
|
|
|
|
cli_set_log_echo(cli *c, unsigned int mask, unsigned int size)
|
|
|
|
{
|
|
|
|
if (c->ring_buf)
|
|
|
|
{
|
|
|
|
mb_free(c->ring_buf);
|
|
|
|
c->ring_buf = c->ring_end = c->ring_read = c->ring_write = NULL;
|
|
|
|
rem_node(&c->n);
|
|
|
|
}
|
|
|
|
c->log_mask = mask;
|
|
|
|
if (mask && size)
|
|
|
|
{
|
|
|
|
c->ring_buf = mb_alloc(c->pool, size);
|
|
|
|
c->ring_end = c->ring_buf + size;
|
|
|
|
c->ring_read = c->ring_write = c->ring_buf;
|
|
|
|
add_tail(&cli_log_hooks, &c->n);
|
|
|
|
c->log_threshold = size / 8;
|
|
|
|
}
|
|
|
|
c->ring_overflow = 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
void
|
|
|
|
cli_echo(unsigned int class, byte *msg)
|
|
|
|
{
|
|
|
|
unsigned len, free, i, l;
|
|
|
|
cli *c;
|
|
|
|
byte *m;
|
|
|
|
|
|
|
|
if (!cli_log_inited || EMPTY_LIST(cli_log_hooks))
|
|
|
|
return;
|
|
|
|
len = strlen(msg) + 1;
|
|
|
|
WALK_LIST(c, cli_log_hooks)
|
|
|
|
{
|
|
|
|
if (!(c->log_mask & (1 << class)))
|
|
|
|
continue;
|
|
|
|
if (c->ring_read <= c->ring_write)
|
|
|
|
free = (c->ring_end - c->ring_buf) - (c->ring_write - c->ring_read + 1);
|
|
|
|
else
|
|
|
|
free = c->ring_read - c->ring_write - 1;
|
2010-02-21 21:34:53 +08:00
|
|
|
if ((len > free) ||
|
|
|
|
(free < c->log_threshold && class < (unsigned) L_INFO[0]))
|
1999-12-06 20:34:45 +08:00
|
|
|
{
|
|
|
|
c->ring_overflow++;
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
if (c->ring_read == c->ring_write)
|
|
|
|
ev_schedule(c->event);
|
|
|
|
m = msg;
|
|
|
|
l = len;
|
|
|
|
while (l)
|
|
|
|
{
|
|
|
|
if (c->ring_read <= c->ring_write)
|
|
|
|
i = c->ring_end - c->ring_write;
|
|
|
|
else
|
|
|
|
i = c->ring_read - c->ring_write;
|
|
|
|
if (i > l)
|
|
|
|
i = l;
|
|
|
|
memcpy(c->ring_write, m, i);
|
|
|
|
m += i;
|
|
|
|
l -= i;
|
|
|
|
c->ring_write += i;
|
|
|
|
if (c->ring_write == c->ring_end)
|
|
|
|
c->ring_write = c->ring_buf;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
1999-10-29 20:10:10 +08:00
|
|
|
void
|
|
|
|
cli_free(cli *c)
|
|
|
|
{
|
1999-12-06 20:34:45 +08:00
|
|
|
cli_set_log_echo(c, 0, 0);
|
1999-11-17 20:00:21 +08:00
|
|
|
if (c->cleanup)
|
|
|
|
c->cleanup(c);
|
1999-10-29 20:10:10 +08:00
|
|
|
rfree(c->pool);
|
|
|
|
}
|
|
|
|
|
2000-06-03 22:40:39 +08:00
|
|
|
/**
|
|
|
|
* cli_init - initialize the CLI module
|
|
|
|
*
|
|
|
|
* This function is called during BIRD startup to initialize
|
|
|
|
* the internal data structures of the CLI module.
|
|
|
|
*/
|
1999-10-29 20:10:10 +08:00
|
|
|
void
|
|
|
|
cli_init(void)
|
|
|
|
{
|
|
|
|
cli_pool = rp_new(&root_pool, "CLI");
|
1999-12-06 20:34:45 +08:00
|
|
|
init_list(&cli_log_hooks);
|
|
|
|
cli_log_inited = 1;
|
1999-10-29 20:10:10 +08:00
|
|
|
}
|