On Mi, 28 iul 10, 16:10:38, Jordon Bedwell wrote:
> On 7/28/10 4:03 PM, Jordan Metzmeier wrote:
> >On 07/28/2010 04:11 PM, Jordon Bedwell wrote:
> >>
> >>find / |grep libraptor
> >
> >Perhaps you wanted find's -name option? find / -name 'libraptor*'
>
> I personally prefer to grep over find, but to each their own :P as
> each have their own methods to do things that ultimately lead to the
> same solution.
Assuming very long output of find, grepping over it is not efficient.
Besides, the file you search might be quite early found and one can
interrupt the search, while with your approach one has to wait until
both find and finish.
Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
07-29-2010, 06:04 AM
Andrei Popescu
find+grep
On Jo, 29 iul 10, 08:41:57, Andrei Popescu wrote:
> On Mi, 28 iul 10, 16:10:38, Jordon Bedwell wrote:
> > On 7/28/10 4:03 PM, Jordan Metzmeier wrote:
> > >On 07/28/2010 04:11 PM, Jordon Bedwell wrote:
> > >>
> > >>find / |grep libraptor
> > >
> > >Perhaps you wanted find's -name option? find / -name 'libraptor*'
> >
> > I personally prefer to grep over find, but to each their own :P as
> > each have their own methods to do things that ultimately lead to the
> > same solution.
>
> Assuming very long output of find, grepping over it is not efficient.
> Besides, the file you search might be quite early found and one can
> interrupt the search, while with your approach one has to wait until
> both find and finish.
grep----------^^^
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
07-29-2010, 09:50 AM
Tzafrir Cohen
find+grep
On Thu, Jul 29, 2010 at 08:41:57AM +0300, Andrei Popescu wrote:
> On Mi, 28 iul 10, 16:10:38, Jordon Bedwell wrote:
> > On 7/28/10 4:03 PM, Jordan Metzmeier wrote:
> > >On 07/28/2010 04:11 PM, Jordon Bedwell wrote:
> > >>
> > >>find / |grep libraptor
> > >
> > >Perhaps you wanted find's -name option? find / -name 'libraptor*'
> >
> > I personally prefer to grep over find, but to each their own :P as
> > each have their own methods to do things that ultimately lead to the
> > same solution.
>
> Assuming very long output of find, grepping over it is not efficient.
> Besides, the file you search might be quite early found and one can
> interrupt the search, while with your approach one has to wait until
> both find and finish.
If you stop it with ctrl-C, both find and grep get interrupted and stop,
right?
--
Tzafrir Cohen | tzafrir@jabber.org | VIM is
http://tzafrir.org.il | | a Mutt's
tzafrir@cohens.org.il | | best
tzafrir@debian.org | | friend
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100729095032.GV17569@pear.tzafrir.org.il">http://lists.debian.org/20100729095032.GV17569@pear.tzafrir.org.il
07-29-2010, 09:57 AM
Andrei Popescu
find+grep
On Jo, 29 iul 10, 09:50:32, Tzafrir Cohen wrote:
>
> If you stop it with ctrl-C, both find and grep get interrupted and stop,
> right?
Actually I don't know how shell pipes work here. Is the output of find
piped to grep only when find finishes or as soon as there is some
output?
Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
07-29-2010, 10:08 AM
Jordon Bedwell
find+grep
On 7/29/10 4:57 AM, Andrei Popescu wrote:
On Jo, 29 iul 10, 09:50:32, Tzafrir Cohen wrote:
If you stop it with ctrl-C, both find and grep get interrupted and stop,
right?
Actually I don't know how shell pipes work here. Is the output of find
piped to grep only when find finishes or as soon as there is some
output?
Regards,
Andrei
As soon as there is an output (which is always immediately) so think of
each iteration of find as being piped to grep, you don't lose *much*
efficiency but you do lose *some*, efficiency is subjective here since
it's CPU time you lose. So if you do a find on root "var and home" would
an iteration (like normal), except instead of staying inside of find
it's piped to grep for each iteration, this is where you lose *some* CPU
time, but you gain a lot more power. You can exit out of the find using
CTRL+C though as somebody did point out CTRL+C is the universal knock
your shit off hot-key for terminals.
I opt to pipe to grep because I usually do a lot more complicated things
with find and over time, I just kept using grep, it's a personal
preference really. Just like using locate is far faster than using find
and find -name is slower and so forth on down the line. I've never been
a big fan of locate though because it can miss on some machines with
horrible i/o.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
07-29-2010, 12:38 PM
Jordan Metzmeier
find+grep
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 07/29/2010 06:08 AM, Jordon Bedwell wrote:
>
> I opt to pipe to grep because I usually do a lot more complicated things
> with find and over time, I just kept using grep, it's a personal
> preference really. Just like using locate is far faster than using find
> and find -name is slower and so forth on down the line. I've never been
> a big fan of locate though because it can miss on some machines with
> horrible i/o.
For me it something that I just cringe to see. I realize that in
practice, it is not bad. I just cannot get over feeling uneasy when
seeing things like:
find | grep
cat | grep
ls -l | grep
for i in $(ls -l foo/)
sudo su
I realize that all of it can be used to accomplish a task. So why do I
hate to see it so much?
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4C517628.1010708@gmail.com">http://lists.debian.org/4C517628.1010708@gmail.com
07-29-2010, 04:22 PM
"Boyd Stephen Smith Jr."
find+grep
On Thursday 29 July 2010 07:38:00 Jordan Metzmeier wrote:
> For me it something that I just cringe to see. I realize that in
> practice, it is not bad. I just cannot get over feeling uneasy when
> seeing things like:
>
> find | grep
> cat | grep
> ls -l | grep
> for i in $(ls -l foo/)
> sudo su
>
> I realize that all of it can be used to accomplish a task. So why do I
> hate to see it so much?
I understand your issues with all but the last one. A user may need to "sudo
su" due to configuration outside of their control. A system that requires you
to "sudo su" for some task is likely misconfigured, but it is a useful tool to
have around, as a user.
The rest are less useful, and generally imply a limited, incomplete, or flawed
understanding of one or more of the tools you are using.
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss@iguanasuicide.net ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/ \_/
07-29-2010, 04:25 PM
Eduardo M KALINOWSKI
find+grep
On Qui, 29 Jul 2010, "Boyd Stephen Smith Jr." wrote:
I understand your issues with all but the last one. A user may need to "sudo
su" due to configuration outside of their control. A system that
requires you
to "sudo su" for some task is likely misconfigured, but it is a
useful tool to
have around, as a user.
sudo -i
--
The optimist thinks that this is the best of all possible worlds,
and the pessimist knows it.
-- J. Robert Oppenheimer, "Bulletin of Atomic Scientists"
Eduardo M KALINOWSKI
eduardo@kalinowski.com.br
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
On 07/29/2010 12:22 PM, Boyd Stephen Smith Jr. wrote:
>
> I understand your issues with all but the last one. A user may need
> to "sudo su" due to configuration outside of their control. A system
> that requires you to "sudo su" for some task is likely misconfigured,
> but it is a useful tool to have around, as a user.
>
> The rest are less useful, and generally imply a limited, incomplete,
> or flawed understanding of one or more of the tools you are using.
I no longer configure my machines in a way that it allows a user to gain
full root via sudo. However, when I did, I found "sudo -i" to be more
appropriate than "sudo su" which seems to be more like "su -l". Of
course, you could always do "sudo su -l".
- From the manpage:
- -i The -i (simulate initial login) option runs the shell specified in
the passwd(5) entry of the user that the command is being run as.
The command name argument given to the shell begins with a ‘-’ to
tell the shell to run as a login shell. sudo attempts to change to
that user’s home directory before running the shell. It also ini‐
tializes the environment, leaving TERM unchanged, setting HOME,
SHELL, USER, LOGNAME, and PATH, and unsetting all other environment
variables. Note that because the shell to use is determined before
the sudoers file is parsed, a runas_default setting in sudoers will
specify the user to run the shell as but will not affect which
shell is actually run.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4C51ACC9.3010901@gmail.com">http://lists.debian.org/4C51ACC9.3010901@gmail.com
find+grep
