Thank you E.Pasma, most elegant. Solves my problem.
Thank you Rowan, I was trying to achieve it with /bin/sh (dash)
On Tue, Sep 18, 2018 at 7:12 PM, E.Pasma wrote:
>
> > Rowan Worth wrote:
> >
> > You can also filter out specific messages at the shell level:
> >
> > sqlite foo.db 2> >(grep -v
> Rowan Worth wrote:
>
> You can also filter out specific messages at the shell level:
>
> sqlite foo.db 2> >(grep -v 'expected 7 columns but found 6 - filling the
> rest with NULL' >&2)
>
> But note that the >() syntax is not a POSIX sh feature, and will not work
> in a script using a shebang
> I have a script that loads csv into an existing table.
>
> I get this message on stderr for each row imported:
>
> "... expected 7 columns but found 6 - filling the rest with NULL"
>
>
> We have the means to send stdout to /dev/null using the .once or .output
>
> Is there a way to send
You can also filter out specific messages at the shell level:
sqlite foo.db 2> >(grep -v 'expected 7 columns but found 6 - filling the
rest with NULL' >&2)
But note that the >() syntax is not a POSIX sh feature, and will not work
in a script using a shebang of #!/bin/sh. You need to change it to
Thanks hick. But that's not the problem.
The import will always write to stderr, it's not an error
Lots of other stuff in the script and I want to be able to catch any errors
in the other parts of the script.
On Tue, Sep 18, 2018 at 4:20 PM, Hick Gunter wrote:
> When running a script from the
When running a script from the shell, you can redirect stderr tot he null
device using 2>/dev/null or to the same destination as stdout using 2>&1. The
latter is also very useful in crontab entries, as neglecting to handle stderr
will result in an email tot he user that contains anything
6 matches
Mail list logo
