On Tue, Jul 05, 2016 at 02:34:20PM -0700, Rick Stevens wrote:
> On 07/05/2016 02:18 PM, Jon LaBadie wrote:
> >
> > There is also "pgrep"
> >
> > $ pgrep chronyd
> > 1542
> >
> > $ pgrep chron
> > 1542
> >
> > $ pgrep fire
> > 1535
> > 8708
> > 21777
> >
> > $ pgrep -l fire
> > 1535 firewalld
On 07/05/2016 02:18 PM, Jon LaBadie wrote:
> On Tue, Jul 05, 2016 at 01:51:48PM -0700, Rick Stevens wrote:
>> On 07/05/2016 01:36 PM, Joe Zeff wrote:
>>> On 07/05/2016 11:35 AM, Rick Stevens wrote:
Yeah, I use that one a lot, too. "pidof -x" is useful as well and you
don't need the
On Tue, Jul 05, 2016 at 01:51:48PM -0700, Rick Stevens wrote:
> On 07/05/2016 01:36 PM, Joe Zeff wrote:
> > On 07/05/2016 11:35 AM, Rick Stevens wrote:
> >> Yeah, I use that one a lot, too. "pidof -x" is useful as well and you
> >> don't need the greps.
> >
> > One of the wonderful things about
On 07/05/2016 01:51 PM, Rick Stevens wrote:
In that sense, your "ps aux | grep | grep -v grep" is a more flexible
in that you only need to know part of the process name. I use it a lot
myself--but not to the point of turning it into a script/utility. :)
In my case, it's not that I use it so
On 07/05/2016 01:36 PM, Joe Zeff wrote:
> On 07/05/2016 11:35 AM, Rick Stevens wrote:
>> Yeah, I use that one a lot, too. "pidof -x" is useful as well and you
>> don't need the greps.
>
> One of the wonderful things about *nix is the fact that there are so
> many different ways to get exactly the
On 07/05/2016 11:35 AM, Rick Stevens wrote:
Yeah, I use that one a lot, too. "pidof -x" is useful as well and you
don't need the greps.
One of the wonderful things about *nix is the fact that there are so
many different ways to get exactly the same results, depending on
personal preference.
On 07/05/2016 11:18 AM, Joe Zeff wrote:
> On 07/05/2016 11:01 AM, Robert Moskowitz wrote:
>> I have GOT to add this to my list of tools
>
> Here's a one-liner that I've used so often I made a shell script out of it:
>
> ps aux | grep $1 | grep -v grep
>
> I will leave the reason for the
On 07/05/2016 11:01 AM, Robert Moskowitz wrote:
I have GOT to add this to my list of tools
Here's a one-liner that I've used so often I made a shell script out of it:
ps aux | grep $1 | grep -v grep
I will leave the reason for the second grep as an exercise for the reader.
--
users
On 07/05/2016 01:50 PM, Joe Zeff wrote:
On 07/05/2016 10:33 AM, Robert Moskowitz wrote:
Been so long since I looked for this info, what is the command for it?
This is a Lenovo x120e
lspci | grep VGA
I have GOT to add this to my list of tools
00:01.0 VGA compatible controller:
On 07/05/2016 10:33 AM, Robert Moskowitz wrote:
Been so long since I looked for this info, what is the command for it?
This is a Lenovo x120e
lspci | grep VGA
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
My calling foul on tumblerd was premature. Other than eating up one
CPU, it was not causing the 'screensaver' problems. I still get it once
in a while, but not like I was getting with the 4.4.13 kernel. I did
kill tumblerd; I was viewing some CDs with wedding pictures via gthumb
yesterday.
On 07/04/2016 08:25 PM, Robert Moskowitz wrote:
Problem seems to be back, and I see tumblerd eating up most of one cpu.
Something I did caused this to run. Can I just kill it or do I need to
kill more than it?
Tumbler appears to be something pulled in by XFCE. It's a dbus service
for
Problem seems to be back, and I see tumblerd eating up most of one cpu.
Something I did caused this to run. Can I just kill it or do I need to
kill more than it?
On 07/04/2016 04:01 PM, Tom Horsley wrote:
On Mon, 4 Jul 2016 15:25:03 -0400
Robert Moskowitz wrote:
Any idea where I should
13 matches
Mail list logo
