Bob Beck wrote:
Changes have been commited to the example syslog.conf in -current
to address this, mainly, stop spewing useless crap to root and the
console.
Normally, I would want it on. But there are times when the output is
annoying, and
I want to shut it off quickly so I can ex
Changes have been commited to the example syslog.conf in -current
to address this, mainly, stop spewing useless crap to root and the
console.
-Bob
* John Draper <[EMAIL PROTECTED]> [2005-06-20 19:47]:
> Stuart Henderson wrote:
>
> >On 2005/06/18 14:41:10, John Draper wrote:
> >
Stuart Henderson wrote:
On 2005/06/18 14:41:10, John Draper wrote:
Quickest way is probably 'pkill syslogd' (or 'kill `cat
/var/run/syslogd.pid`'
if you don't have pkill).
...or just login as a user other than root, and use "sudo" to execute the
commands...
Ok, if I do that, t
Moritz Grimm wrote:
I cannot do that - the box is over 500KM away from me.
Well, okay, but calling the ISP for help in case of DoS is still
something you should do - if the source(s) of the attack come from a
reasonably small portion of the 'net, they can null-route those
networks, giving
On Sat, Jun 18, 2005 at 02:47:03PM -0700, John Draper wrote:
> But the "pkill syslogd" seems a reasonable thing to do, but how do I
> set it back again? One other problem I have is my "ps" don't work,
> but that problem is going to be fixed in my next scheduled upgrade.
If ps doesn't work, there
On 2005/06/18 14:47:03, John Draper wrote:
> >Log in as a regular user, the su to root and edit /etc/syslog.conf and
> >don't send stuff to the console anymore. A SIGHUP to syslogd should
> >suffice.
>
> I don't have any reg user in "wheel".
# usermod -G wheel someuser
Moritz Grimm wrote:
John Draper wrote:
We are getting attacked, but our "root" console is outputting log data
so fast we can't ussue any "root" commands.
What can I do to temporarily stop the console output so I can ussue
a few "root" commands to change our FW settings?
Log in as a regular
On 6/18/05, John Draper <[EMAIL PROTECTED]> wrote:
> Hi,
>
> We are getting attacked, but our "root" console is outputting log data
> so fast we can't ussue any "root" commands.
>
> What can I do to temporarily stop the console output so I can ussue
> a few "root" commands to change our FW settin
On 2005/06/18 14:04:27, John Draper wrote:
> We are getting attacked, but our "root" console is outputting log data
> so fast we can't ussue any "root" commands.
Quickest way is probably 'pkill syslogd' (or 'kill `cat /var/run/syslogd.pid`'
if you don't have pkill).
...or just login as a user oth
Hi,
We are getting attacked, but our "root" console is outputting log data
so fast we can't ussue any "root" commands.
What can I do to temporarily stop the console output so I can ussue
a few "root" commands to change our FW settings?
JD
10 matches
Mail list logo
