From: Yapo Sebastien <sebastien.yapo@e-neyret.com>
To: linux-newbie@vger.kernel.org
Subject: Re: unusual uniq results
Date: Wed, 29 Sep 2004 14:53:19 +0000 [thread overview]
Message-ID: <200409291453.19686.sebastien.yapo@e-neyret.com> (raw)
In-Reply-To: <fc.004c4e00006491a0004c4e0000647133.6491aa@palmertrinity.org>
Well ... the main problem is that the bash redirection takes effect before
uniq is executed.
When you do "uniq dup_num > dup_num" the following happens :
- the bash redirection operator ">" triggers the opening of dup_num in
write-only mode (O_WRONLY | O_CREAT | O_TRUNC) to redirect stdout to the
file, thus truncating dup_num to zero length as the file already exists
- the file dup_num is opened read-only by uniq (O_RDONLY)
- the output stream is assumed by uniq to be stdout (no "OUTFILE" specified)
- each line of dup_num is read and treated by uniq but dup_num is empty
(truncated to zero length before) so, obviously, the result of uniq is also
empty.
This is probably not perfectly accurate but is "grosso modo" what happens.
Quote from bash manual (Redirection / Redirecting Output) :
"If the file does not exist it is created; if it does exist it is truncated to
zero size."
Sebastien
On Wednesday 29 September 2004 11:07, you wrote:
> I'm confused. To me the > has always meant to take what is to the left of
> the sign and redirect its output to whatever is to the right. In my case
> this would mean taking the output of uniq dup_num and redirecting it. Can
> you set me straight?
> -- Bill
>
> Stone <xstonedogx@gmail.com> writes:
> >The redirection takes place before your command. So basically what
> >you told the system to do was:
> >
> >1. Create the file dup_num. If the file exists overwrite it.
> >2. Redirect stdout of "uniq dup_num" into dup_num.
> >
> >Since you'd already overwritten the data in dup_num, there was nothing
> >for uniq to process.
> >
> >On Tue, 28 Sep 2004 11:09:12 -0400, William Stanard
> >
> ><wstanard@palmertrinity.org> wrote:
> >> In doing a demo before a class (Linux Red-hat 2.4.18-14), I used the
> >
> >uniq
> >
> >> command on a file (dup_nums) that consisted of twelve lines, each line
> >> containing a number, from one to 9. I repeated the numbers, 6, 8, and 9.
> >> The std output showed the expected list of numbers, all duplicates
> >> removed. At a student's suggestion, I ran uniq again, but this time
> >> directed the output to the file itself....
> >>
> >> uniq dup_num > dup_num
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
prev parent reply other threads:[~2004-09-29 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 15:09 unusual uniq results William Stanard
2004-09-28 16:11 ` Stone
2004-09-29 11:07 ` William Stanard
2004-09-29 12:44 ` Simon Valiquette
2004-09-29 14:53 ` Yapo Sebastien [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200409291453.19686.sebastien.yapo@e-neyret.com \
--to=sebastien.yapo@e-neyret.com \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox