On 8/23/19 5:21 PM, Neil Bothwick wrote:
> On 22 August 2019 22:08:41 GMT-04:00, Andrew Udvare wrote:
>>
>>> On 2019-08-22, at 12:31, Laurence Perkins
>> wrote:
>>>
>>> A common tactic is to use grep twice:
>>> ps auxf | grep -v grep | grep blah
>>
>> Or grep with brackets:
>>
>> ps aux | grep
On 22 August 2019 22:08:41 GMT-04:00, Andrew Udvare wrote:
>
>> On 2019-08-22, at 12:31, Laurence Perkins
>wrote:
>>
>> A common tactic is to use grep twice:
>> ps auxf | grep -v grep | grep blah
>
>Or grep with brackets:
>
>ps aux | grep '[f]irefox'
>
>I have a function for this:
>
>psgrep() {
> On 2019-08-22, at 12:31, Laurence Perkins wrote:
>
> A common tactic is to use grep twice:
> ps auxf | grep -v grep | grep blah
Or grep with brackets:
ps aux | grep '[f]irefox'
I have a function for this:
psgrep() {
ps aux | grep "[${1:0:1}]${1:1}";
}
This works because the ps output
On 2019.08.22 12:31, Laurence Perkins wrote:
On Thu, 2019-08-22 at 10:03 +1000, Adam Carter wrote:
> On Thu, Aug 22, 2019 at 5:48 AM james wrote:
> > On 8/16/19 12:44 PM, Jack wrote:
> > > ps auxf | grep systemd
> >
> > This is new turf for me. Upon issuing this command string I get::
> >
> >
On Thu, 2019-08-22 at 10:03 +1000, Adam Carter wrote:
> On Thu, Aug 22, 2019 at 5:48 AM james wrote:
> > On 8/16/19 12:44 PM, Jack wrote:
> > > ps auxf | grep systemd
> >
> > This is new turf for me. Upon issuing this command string I get::
> >
> > # ps auxf | grep systemd
> > root 24947
On Thu, Aug 22, 2019 at 5:48 AM james wrote:
> On 8/16/19 12:44 PM, Jack wrote:
> > ps auxf | grep systemd
>
> This is new turf for me. Upon issuing this command string I get::
>
> # ps auxf | grep systemd
> root 24947 0.0 0.0 13964 996 pts/6S+ 15:43 0:00
> | | |
On 2019.08.21 15:48, james wrote:
On 8/16/19 12:44 PM, Jack wrote:
> ps auxf | grep systemd
This is new turf for me. Upon issuing this command string I get::
# ps auxf | grep systemd
root 24947 0.0 0.0 13964 996 pts/6S+ 15:43 0:00
| | | \_ grep
On 8/16/19 12:44 PM, Jack wrote:
> ps auxf | grep systemd
This is new turf for me. Upon issuing this command string I get::
# ps auxf | grep systemd
root 24947 0.0 0.0 13964 996 pts/6S+ 15:43 0:00
| | | \_ grep --colour=auto systemd
I have no clue
On 08/16/2019 06:21:30 PM, Jack wrote:
On 2019.08.16 12:00, Helmut Jarausch wrote:
On 08/16/2019 05:25:34 PM, Jack wrote:
try "lsof /cdrom"? It says the mount point, not the device, might
be busy.
This didn't show anything.
I still don't know the cause of my problems.
But fortunately,
On Fri, 2019-08-16 at 12:21 -0400, Jack wrote:
> On 2019.08.16 12:00, Helmut Jarausch wrote:
> > On 08/16/2019 05:25:34 PM, Jack wrote:
> > > try "lsof /cdrom"? It says the mount point, not the device,
> > > might
> > > be busy.
> >
> > This didn't show anything.
> > I still don't know the
On 2019.08.16 12:26, Helmut Jarausch wrote:
On 08/16/2019 05:25:34 PM, Jack wrote:
try "lsof /cdrom"? It says the mount point, not the device, might
be busy.
Unfortunately, the problem is still there.
dmesg shows
[ 1326.461161] systemd-udevd[9882]: Process 'cdrom_id --eject-media
On 08/16/2019 05:25:34 PM, Jack wrote:
try "lsof /cdrom"? It says the mount point, not the device, might be
busy.
Unfortunately, the problem is still there.
dmesg shows
[ 1326.461161] systemd-udevd[9882]: Process 'cdrom_id --eject-media
/dev/sr0' failed with exit code 1.
But does that
On 2019.08.16 12:00, Helmut Jarausch wrote:
On 08/16/2019 05:25:34 PM, Jack wrote:
try "lsof /cdrom"? It says the mount point, not the device, might
be busy.
This didn't show anything.
I still don't know the cause of my problems.
But fortunately, they have been resolved by recompiling the
On 08/16/2019 05:25:34 PM, Jack wrote:
try "lsof /cdrom"? It says the mount point, not the device, might be
busy.
This didn't show anything.
I still don't know the cause of my problems.
But fortunately, they have been resolved by recompiling the kernel
(5.2.0),
systemd and all packages
try "lsof /cdrom"? It says the mount point, not the device, might be busy.
On 8/16/19 10:23 AM, Helmut Jarausch wrote:
Hi,
I have a very strange effect on my Gentoo system.
First, I've check that /dev/sr0 points to the correct device (from dmesg)
For an empty drive I get
1 # mount /dev/sr0
On 08/16/2019 05:22:27 PM, J. Roeleveld wrote:
Sounds like error message is not clear. But as there is no disc, the
mount
action should fail anyway.
What happens when there is a disc in the drive?
The same unfortunately.
Thanks,
Helmut
--
Joost
On 16 August 2019 16:23:36 CEST, Helmut
Sounds like error message is not clear. But as there is no disc, the mount
action should fail anyway.
What happens when there is a disc in the drive?
--
Joost
On 16 August 2019 16:23:36 CEST, Helmut Jarausch wrote:
>Hi,
>
>I have a very strange effect on my Gentoo system.
>First, I've check
Hi,
I have a very strange effect on my Gentoo system.
First, I've check that /dev/sr0 points to the correct device (from
dmesg)
For an empty drive I get
1 # mount /dev/sr0 /cdrom
mount: /cdrom: /dev/sr0 already mounted or mount point busy.
2 # lsof /dev/sr0
3 # umount /dev/sr0
umount:
18 matches
Mail list logo
