Tony Sequeira wrote:
On Fri, 2006-09-22 at 19:49 +0200, Brandon Peirce wrote:
> Christopher Parker wrote:
>
> >The source of this problem was due to GAWK not parsing the parameters
> >correctly. I now have the problem that the following command
> >
> >echo "parm1 parm2" | awk '{print $1}'
> >
>
On 9/22/06, Jeremy Henty <[EMAIL PROTECTED]> wrote:
LFS installs a fairly standard looking syslog.conf but doesn't explain
its contents. I'm wondering if there is any justification for
splitting the log messages to different files? There's so much to
wade through you'll be using some log analy
Jeremy Henty stated:
> LFS installs a fairly standard looking syslog.conf but doesn't explain
> its contents. I'm wondering if there is any justification for
> splitting the log messages to different files? There's so much to
> wade through you'll be using some log analysis/monitoring program
> a
On Fri, 2006-09-22 at 19:49 +0200, Brandon Peirce wrote:
> Christopher Parker wrote:
>
> >The source of this problem was due to GAWK not parsing the parameters
> >correctly. I now have the problem that the following command
> >
> >echo "parm1 parm2" | awk '{print $1}'
> >
> >resolves to "parm1 p
Christopher Parker wrote:
The source of this problem was due to GAWK not parsing the parameters
correctly. I now have the problem that the following command
echo "parm1 parm2" | awk '{print $1}'
resolves to "parm1 parm2" instead of just "parm1". Has anyone seen this
before, or have any sug
