bug-grep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#56843: grep mangling lines


From: Dimitry Andric
Subject: bug#56843: grep mangling lines
Date: Sat, 30 Jul 2022 19:15:49 +0200

On 30 Jul 2022, at 17:57, David G. Pickett via Bug reports for GNU grep 
<bug-grep@gnu.org> wrote:
> 
> I was stunned to see the grep command remove bytes:
> 
> $ crontab -l|grep clam30 23 * * * /usr/bin/freshclam 
> --datadir=/home/dgp/.clamtk/db 
> --log=/home/dgp/.clamtk/db/freshclam.$(/bin/date +\%b-\%d-\%Y).log 
> >/home/dgp/.clamtk/db/freshcla_cron.log 2>&1 ; /usr/local/bin/clamdscan 
> --config-file=/etc/clamav/clamd.conf --reload 
> --log="$HOME/.clamtk/history/$(/bin/date +\%b-\%d-\%Y).log" 
> >>.clamtk/history/clamscan.log 2>&1 ; /usr/local/bin/clamdscan 
> --config-file=/etc/clamav/clad.conf --quiet --multiscan --fdpass 
> --log="$HOME/.clamtk/history/$(/bin/date +\%b-\%d-\%Y).log" $HOME 
> >>.clamtk/history/clamscan.log 2>&1 # freshclam update andclam-scan
> from this line:
> 30 23 * * * /usr/bin/freshclam --datadir=/home/dgp/.clamtk/db 
> --log=/home/dgp/.clamtk/db/freshclam.$(/bin/date +\%b-\%d-\%Y).log 
> >/home/dgp/.clamtk/db/freshclam_cron.log 2>&1 ; /usr/local/bin/clamdscan 
> --config-file=/etc/clamav/clamd.conf --reload 
> --log="$HOME/.clamtk/history/$(/bin/date +\%b-\%d-\%Y).log" 
> >>.clamtk/history/clamscan.log 2>&1 ; /usr/local/bin/clamdscan 
> --config-file=/etc/clamav/clamd.conf --quiet --multiscan --fdpass 
> --log="$HOME/.clamtk/history/$(/bin/date +\%b-\%d-\%Y).log" $HOME 
> >>.clamtk/history/clamscan.log 2>&1 # freshclam update and clam-scan
> On my 80x25 xterm, the missing byte should have been at the end of the line, 
> and is highlighted in red.  Highlighting is ok but accurate data is nicer?

I'm sorry, but the formatting in your mail seems completely mangled. ;)

It's very hard to make out what you think is wrong, so could you make
that more explicit?

-Dimitry






reply via email to

[Prev in Thread] Current Thread [Next in Thread]