It is an age thing. The older you get the harder it is to remeber the minor bits. It is not so much an issue of remembering as it is on retrival. Just to much to sift through sometimes. But you are ignoring alot in the examples I showed. If I know a little about what I want I will be very likely to get what I want with a grep but I will always get negatives if I am even one character off on a strait chkconfig --list (foo). If I get a negative response with a grep I know I am alot further off than I thought I was, and shell history works just as well with grep. I also noticed you ignored completely the second example where I was looking at multiple associated services. One command line arg my way 4 yours. Happy grep(ing). BTW awk is pretty cool too. Yes I know you can do it in perl. This is a rather extraordinary amount of verbage for just 6 characters. -----Original Message----- From: Michael Schwendt [mailto:rh0210ms@arcor.de] Sent: Fri, December 13, 2002 11:57 AM To: psyche-list@redhat.com Subject: Re: Telnet with RH8.0 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 13 Dec 2002 07:51:21 -0800, Jesse Keating wrote: > > Hehe. :) Consider yourself lucky. But it's not convincing enough. > > Watch this: > > > > $ /sbin/chkconfig --list | grep news > > $ /sbin/chkconfig --list | grep nntp > > $ /sbin/chkconfig --list leafnode > > leafnode on > > Huh? what does this prove? Uhm, it doesn't prove anything. It is just one reason why I'm not convinced that "chkconfig --list | grep foo" is any better than "chkconfig --list foo". Because if I let "grep" search for a wrong pattern, it doesn't find anything either. It all boils down to whether you have every service name in your head. If you think the web service is called "apache", the following two commands would both fail: $ /sbin/chkconfig --list | grep apach $ /sbin/chkconfig --list apache error reading information on service apache: No such file or directory Forgetting the 'd' at the end of "chkconfig --list http" may happen, but using shell history it can be added easily. The message was a reply to: > Yes but my way always works. Which in the long run will save you > typing and frustration. > ]$ chkconfig --list http > error reading information on service http: No such file or directory > ]$ chkconfig --list |grep http > httpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off > ]$ chkconfig --list yp > error reading information on service yp: No such file or directory > ]$ chkconfig --list |grep yp > ypbind 0:off 1:off 2:off 3:on 4:on 5:on 6:off > yppasswdd 0:off 1:off 2:off 3:off 4:off 5:off 6:off > ypserv 0:off 1:off 2:off 3:off 4:off 5:off 6:off > ypxfrd 0:off 1:off 2:off 3:off 4:off 5:off 6:off - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) iD8DBQE9+hFe0iMVcrivHFQRAkCyAJ42G4QV9LnlWk7LkzUsoFfhbc/3UwCfX7bI TJqR8Qa9yqGYbU4lRaA81vM= =4Uxw -----END PGP SIGNATURE----- -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
