On Friday 05 October 2012 07:42:33 Geert Stappers wrote:
> Here a less evil trick, execute from shell
>
>echo messages | /etc/bacula/scripts/bconsole > /dev/null
>
> Put it in a cronjob that runs at night
> to have each moring a (nearly) empty message buffer.
>
>
> Cheers
> Geert Stappers
Nice
Op 20121003 om 15:05 schreef Dan Langille:
> On 2012-09-28 07:00, Gary Stainburn wrote:
> > I don't log into bconsole for maybe a week at at time and when I do
> > I'm usually messing about with config settings.
> >
> > I tend to always run 'auto on' as the first command but can sometimes
> > have
On 2012-09-28 07:00, Gary Stainburn wrote:
> I don't log into bconsole for maybe a week at at time and when I do
> I'm
> usually messing about with config settings.
>
> I tend to always run 'auto on' as the first command but can sometimes
> have to
> wait over 5 minutes for a week's worth of log e
Hello,
2012/10/1 Gary Stainburn
> Is there a way to dynamically turn message logging off / on?
>
>
I don't know.
> I use the console logging while working in bconsole but don't need it the
> rest
> of the time.
>
I think you can simply truncate a console message buffer before issuing a
bconso
On Sunday 30 September 2012 00:54:14 Radosław Korzeniewski wrote:
> Hello,
>
> 2012/9/28 Gary Stainburn
> > Is there a way to limit the entries displayed to say the last 4 hours, or
> > the
> > last 1000 lines?
>
> No. But you can simply disable console messages.
Is there a way to dynamically tur
Hello,
2012/9/28 Gary Stainburn
> I don't log into bconsole for maybe a week at at time and when I do I'm
> usually messing about with config settings.
>
> I tend to always run 'auto on' as the first command but can sometimes have
> to
> wait over 5 minutes for a week's worth of log entries to s
I don't log into bconsole for maybe a week at at time and when I do I'm
usually messing about with config settings.
I tend to always run 'auto on' as the first command but can sometimes have to
wait over 5 minutes for a week's worth of log entries to scroll up my screen.
Is there a way to limit
Log to syslog:
# Message delivery for daemon messages (no job).
Messages {
Name = Daemon
syslog = all, !skipped
}
---
syslog-ng.conf:
destination baculadirlog { file("/var/log/bacula-dir.log"
template("$FULLDATE $TZ $HOST [$PROGRAM][$PID] [$FACILITY] [$LEVEL] $MSG
\n") ); }
filter
I would like to know if there is a way to have the messages all be
logged, but not sent to the console unless the console is active -- I
don't plan to be looking at the console much once a system is up and
running, but having hundreds of messages scroll past when you log in
is at least annoying.
~
Hi,
On 6/14/2007 3:07 PM, le dahut wrote:
> Must the console messages (bconsole => "messages") be flushed regularly
> or is there a configuration option telling not to store the messages or
> can it stay "as it is" ?
As fa as I know the console messages are buffered on disk. You don't
have to
Must the console messages (bconsole => "messages") be flushed regularly
or is there a configuration option telling not to store the messages or
can it stay "as it is" ?
K.
-
This SF.net email is sponsored by DB2 Express
D
On Friday 29 September 2006 04:41 pm, Kern Sibbald wrote:
> On Friday 29 September 2006 23:19, Michael Brennen wrote:
> > Offhand I don't see a good way in the Console resource to restrict
> > message access. Is the best option for the moment simply to disable
> > console message support and depe
On Friday 29 September 2006 23:19, Michael Brennen wrote:
>
> I just logged into Bacula from a client machine that has tighly restricted
> access. It can only access its own pools, jobs, etc.
>
> When I logged in with wx-console I was surprised by a sudden flood of queued
> console messages fo
On Friday 29 September 2006 23:19, Michael Brennen wrote:
>
> I just logged into Bacula from a client machine that has tighly restricted
> access. It can only access its own pools, jobs, etc.
>
> When I logged in with wx-console I was surprised by a sudden flood of queued
> console messages fo
I just logged into Bacula from a client machine that has tighly restricted
access. It can only access its own pools, jobs, etc.
When I logged in with wx-console I was surprised by a sudden flood of queued
console messages for all jobs from last night. Those messages of course give
quite a bi
15 matches
Mail list logo
