That should give you an error, as /dev/null usually isn't executable. I don't know what it's behavior would be if you made it executable, offhand. It's the difference between these two:
$ ls | cat > /dev/null $ ls | /dev/null bash: /dev/null: Permission denied On Fri, 2005-11-18 at 14:12 -0800, Micah Stevens wrote: > I've been piping to dev/null directly, and it works for me. What's wrong with > that? > > > > On Friday 18 November 2005 1:10 pm, Jesse Norell wrote: > > To actually put it all in /dev/null, you'd have to use something like > > '| /bin/cat > /dev/null' .. but it might be more efficient to use > > '| /bin/true' (since true(1) won't read all the data from stdin and > > write to stdout, just to be discarded). Nothing else very clever > > comes to mind (dbmail doesn't support anything like '> /dev/null' to > > write directly to a file), but perhaps with the upcoming sieve > > support you could just tell it to delete a message and be more efficient > > yet. > > > > On Fri, 2005-11-18 at 21:36 +0200, [EMAIL PROTECTED] wrote: > > > Hi, > > > > > > How to deliver mail to /dev/null using aliases table? > > > > > > > > > Thanks, > > > Igor. > > > > > > _______________________________________________ > > > Dbmail mailing list > > > Dbmail@dbmail.org > > > https://mailman.fastxs.nl/mailman/listinfo/dbmail -- Jesse Norell - [EMAIL PROTECTED] Kentec Communications, Inc.
