On 6/25/2012 8:25 AM, Bill Davidsen wrote:
Paul Allen Newell wrote:
On 5/21/2012 5:48 AM, Tim wrote:
On Sun, 2012-05-20 at 11:35 -0700, Paul Allen Newell wrote:
I am having problems with is expecting to see new additions from
iptables logging rejections and not getting them until much later, i
Paul Allen Newell wrote:
On 5/21/2012 5:48 AM, Tim wrote:
On Sun, 2012-05-20 at 11:35 -0700, Paul Allen Newell wrote:
I am having problems with is expecting to see new additions from
iptables logging rejections and not getting them until much later, if
at all? I just wanted to find out if there
On 5/22/2012 1:01 PM, Bill Davidsen wrote:
/etc/rsyslog.conf and it's man page. Define a debug.log and have debug
stuff go there, by setting the level to debug.
Bill:
Once again, thanks for the link
Paul
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscr
On 5/22/2012 12:56 PM, Bill Davidsen wrote:
tail -0f /var/log/messages
You get the existing lines you ask for, ten by default. And there is a
buffering option in syslogd, I just don't recall where I used to set
it. I believe by default it's line buffered, output at newline.
Bill:
Thanks
On 5/22/2012 1:05 PM, Bill Davidsen wrote:
From part of my firewall startup, a few LOG calls wehich might help.
# LOG and REJECT anything which looks like a probe
iptables -N PROBE
iptables -A PROBE -j LOG --log-level debug --log-prefix PROBE:
iptables -A PROBE -j REJECT --reject-with icmp-ho
Paul Allen Newell wrote:
On 5/21/2012 5:07 PM, Max Pyziur wrote:
One more suggestion; if I understand correctly, you want to tail -f a logfile,
but you only want to see certain events; perhaps this is what you need:
tail -f /path/to/some/logfile | grep certain_event
Paul
fyi,
Max Pyziu
Paul Allen Newell wrote:
On 5/21/2012 5:48 AM, Tim wrote:
On Sun, 2012-05-20 at 11:35 -0700, Paul Allen Newell wrote:
I am having problems with is expecting to see new additions from
iptables logging rejections and not getting them until much later, if
at all? I just wanted to find out if there
Mikkel L. Ellertson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/19/2012 11:51 PM, Paul Allen Newell wrote:
Hello:
Is there a way to flush output to /etc/log/message so a tail -f
catches things when they happen rather than what I think I am
seeing as a buffer hold-until-full de
Mon, 21 May 2012 18:25:44 -0700
Paul Allen Newell kirjoitti:
> To be honest, now that I found out that the problem with ssh from F16
> to Cygwin was POM on the Windows side (and notice I am not limiting
> to just Cygwin (smile)), it has become "not so important". But some
> of the suggestions lo
On 5/21/2012 5:07 PM, Max Pyziur wrote:
One more suggestion; if I understand correctly, you want to tail -f a
logfile, but you only want to see certain events; perhaps this is what
you need:
tail -f /path/to/some/logfile | grep certain_event
Paul
fyi,
Max Pyziur
p...@brama.com
Max:
On Sun, 20 May 2012, Paul Allen Newell wrote:
On 5/20/2012 5:20 AM, Mikkel L. Ellertson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/19/2012 11:51 PM, Paul Allen Newell wrote:
> Hello:
>
> Is there a way to flush output to /etc/log/message so a tail -f
>catches things
On 5/21/2012 1:19 PM, Alan J. Gagne wrote:
On 5/21/2012 12:15 PM, Alan J. Gagne wrote:
>/
/>/ You could look at sending iptables messages to /var/log/iptables using
/>/ rsyslog.
/>/
/>/
http://blog.shadypixel.com/log-iptables-messages-to-a-separate-file-with-rsyslog/
/>/
/>/ Alan
/>/
/>/
/
A
On 5/21/2012 12:15 PM, Alan J. Gagne wrote:
>/
/>/ You could look at sending iptables messages to /var/log/iptables using
/>/ rsyslog.
/>/
/>/
http://blog.shadypixel.com/log-iptables-messages-to-a-separate-file-with-rsyslog/
/>/
/>/ Alan
/>/
/>/
/
Alan:
Thanks for the reply. I did an initial
On 5/21/2012 12:15 PM, Alan J. Gagne wrote:
You could look at sending iptables messages to /var/log/iptables using
rsyslog.
http://blog.shadypixel.com/log-iptables-messages-to-a-separate-file-with-rsyslog/
Alan
Alan:
Thanks for the reply. I did an initial read of the page and it looks
When I first looked into the man pages et al for iptables, I found the
LOG but no way to specify a file. The best I could sort out was using a
prefix so I would at least have a token to search for in /var/log/messages.
I just did a quick google to see if I missed something. The only thing I
see i
On 5/21/2012 5:48 AM, Tim wrote:
On Sun, 2012-05-20 at 11:35 -0700, Paul Allen Newell wrote:
I am having problems with is expecting to see new additions from
iptables logging rejections and not getting them until much later, if
at all? I just wanted to find out if there was a need/way to make su
On Sun, 2012-05-20 at 11:35 -0700, Paul Allen Newell wrote:
> I am having problems with is expecting to see new additions from
> iptables logging rejections and not getting them until much later, if
> at all? I just wanted to find out if there was a need/way to make sure
> that nothing is "waiting"
On 5/20/2012 5:20 AM, Mikkel L. Ellertson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/19/2012 11:51 PM, Paul Allen Newell wrote:
Hello:
Is there a way to flush output to /etc/log/message so a tail -f
catches things when they happen rather than what I think I am
seeing as a buf
Am 20.05.2012 14:52, schrieb suvayu ali:
> On Sun, May 20, 2012 at 2:20 PM, Mikkel L. Ellertson
> wrote:
>>
>> What you are seeing is the last last 10 lines of the file, and
>> then new additions as it is added to the file. This is the way
>> tail -f works. You may want to read the man or info p
On Sun, May 20, 2012 at 2:20 PM, Mikkel L. Ellertson
wrote:
>
> What you are seeing is the last last 10 lines of the file, and
> then new additions as it is added to the file. This is the way
> tail -f works. You may want to read the man or info page on tail.
Maybe `less +F /path/to/file` would b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/19/2012 11:51 PM, Paul Allen Newell wrote:
> Hello:
>
> Is there a way to flush output to /etc/log/message so a tail -f
> catches things when they happen rather than what I think I am
> seeing as a buffer hold-until-full delay?
>
> Thanks in a
On 05/19/2012 11:51 PM, Paul Allen Newell wrote:
Hello:
Is there a way to flush output to /etc/log/message so a tail -f
catches things when they happen rather than what I think I am seeing
as a buffer hold-until-full delay?
Thanks in advance,
Paul
output of what?
See
logger (1) - a
Hello:
Is there a way to flush output to /etc/log/message so a tail -f catches
things when they happen rather than what I think I am seeing as a buffer
hold-until-full delay?
Thanks in advance,
Paul
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription opti
23 matches
Mail list logo