On 08/09/2017 06:14 PM, Rick Stevens wrote:
You have to have at least two "part raid.somenumber" lines to create a
RAID1, and a "raid" line to define the type of RAID, filesystem type
and mountpoint.
I did. I used a kickstart that was as close to D&R's snippet as possible.
Have a look at:
On 08/10/2017 10:07 AM, bruce wrote:
> the test was to (1) replicate the results I get from the cmdline.
> and to then (2) be able to pass a input/var to then generate the pgrep
> count results
>
> the initial cmdline pgrep -- pgrep -f 'bash' | wc -l
> -- on the test box, this returns a "50" coun
hey guys...
appears to be user error... looks like i was on the wrong/older box..
on the updated centos/fed.. looks as i expected... at least for now!
thanks..
On Wed, Aug 9, 2017 at 10:07 PM, bruce wrote:
> On Wed, Aug 9, 2017 at 9:52 PM, kevin martin wrote:
>> is the end result meant to be
On Wed, Aug 9, 2017 at 9:52 PM, kevin martin wrote:
> is the end result meant to be able to pass some string ($1) to pgrep that
> get's counted? knowing what you're trying to accomplish would make it
> easier to help.
>
> ---
>
-
hey kevin. sorry.
the test was to (1) replicate the
On 08/09/2017 05:47 PM, bruce wrote:
aa='bash'
xx="pgrep -f '"${aa}"' | wc -l"
echo $xx <<< this dsplays the test pgrep
echo `$xx` << err msg
echo `${xx}` << err msg...
eval "$xx"
or:
echo $(eval "$xx")
In the invocation you're trying to use, "|" is being passed as an
argument to pgre
is the end result meant to be able to pass some string ($1) to pgrep that
get's counted? knowing what you're trying to accomplish would make it
easier to help.
---
Regards,
Kevin Martin
On Wed, Aug 9, 2017 at 8:24 PM, bruce wrote:
> h update..
>
> this works...
> aa='bash'
> echo $aa
h update..
this works...
aa='bash'
echo $aa " pp"
xx= pgrep -f $aa | wc -l
echo $xx
however, I can't seem to figure out how to enclose the aa var in
single quotes within the pgrep.
thoughts/comments..
thanks
On Wed, Aug 9, 2017 at 8:47 PM, bruce wrote:
> trying to get the following t
On 08/09/2017 04:02 PM, Gordon Messmer wrote:
> On 08/09/2017 02:27 PM, Rick Stevens wrote:
>> Right below those "part" definitions, you see "raid" definitions where
>> those labels are normally used. In your case,
>>
>> raid / --device=root --fstype=ext4 --level=raid1 --useexisting
>>
>> tells
unclear what you are trying to accomplish here. If, for example, you are
trying to pgrep for all processes that have 'bash' in the process name:
#!/bin/bash
aa='bash'
xx="pgrep -f ${aa} | wc -l"
echo $xx <<< shows the command in $xx
eval ${xx} <<< runs the command in $xx
---
Regards,
Kevin Ma
On 08/09/2017 05:47 PM, bruce wrote:
> trying to get the following to output
> pgrep -f 'bash' | wc -l
>
> the var $xx has the cmd...
> something's missing to allow the backtics to run the cmd..
> if the cmd is hadcoded.run, it works..
>
> can't see what the homer simpson "doh" moment is!
trying to get the following to output
pgrep -f 'bash' | wc -l
the var $xx has the cmd...
something's missing to allow the backtics to run the cmd..
if the cmd is hadcoded.run, it works..
can't see what the homer simpson "doh" moment is!
thanks
#!/bin/bash
#
# ptest.sh
#
# use predefin
On 08/09/2017 02:27 PM, Rick Stevens wrote:
Right below those "part" definitions, you see "raid" definitions where
those labels are normally used. In your case,
raid / --device=root --fstype=ext4 --level=raid1 --useexisting
tells the system to use the first two devices in the "part" sec
On Wed, Aug 09, 2017 at 02:06:20PM -0400, bruce wrote:
> Hey peeps.
>
> From a fed/centos cmdline...
>
> pgrep -f "foo" | wc -l
>
> will return 0 -- if "foo" doesn't exist in the procTBL, and something
> else if "foo" is running.
>
> The curiousity... When I have a simple php
>
>
> $f="pgre
On 08/09/2017 12:08 PM, D&R wrote:
> On Wed, 9 Aug 2017 12:00:00 -0700
> Rick Stevens wrote:
>
>> On 08/09/2017 11:52 AM, D&R wrote:
>>> When I boot into the install there is an error in the destination section.
>>>
>>> I looked at the debug info in the storage.log and there was an
>>> error abou
On 08/09/2017 11:52 AM, D&R wrote:
I looked at the debug info in the storage.log and there was an
error about sdb1 did not exist. But...
Switch to VT2 (where I assume you examined storage.log) and run "ls -l
/dev/sd* /dev/md" or "lsblk" to see what block devices *do* exist.
You want to make
On Wed, 2017-08-09 at 14:06 -0400, bruce wrote:
> Hey peeps.
>
> From a fed/centos cmdline...
>
> pgrep -f "foo" | wc -l
>
> will return 0 -- if "foo" doesn't exist in the procTBL, and something
> else if "foo" is running.
>
> The curiousity... When I have a simple php
>
>
> $f="pgrep -f 'f
On 08/09/2017 01:48 PM, Craig Lanning wrote:
On Wed, 2017-08-09 at 08:52 -0700, Thomas Dineen wrote:
Gentle People:
I hate to interrupt your Fedora 26 party, but well here goes a
dose of reality from the
USER's PROSPECTIVE!
Yours is not *the* user's perspective. Yours is *a* user's persp
On Wed, 9 Aug 2017 08:52:59 -0700, Thomas Dineen wrote:
> Gentle People:
^^
That doesn't match the tone you've used in some of your rants.
> I want Text Editors, shell Windows, gcc, gdb , and ddd.
> 6) Yum and rpm: Please print to the screen the directories where S/W is
> installed. So th
On Wed, 9 Aug 2017 12:00:00 -0700
Rick Stevens wrote:
> On 08/09/2017 11:52 AM, D&R wrote:
> > When I boot into the install there is an error in the destination section.
> >
> > I looked at the debug info in the storage.log and there was an
> > error about sdb1 did not exist. But...
> >
> > Whe
On 9 August 2017 at 16:52, Thomas Dineen wrote:
> 8) Are you on drugs? ... Please consider carefully the possibility that you
> are going in the
> wrong direction!
I suggest you go back to where you purchased the software and ask for
a full refund. Seriously, file a decent bug report and we can
On 08/09/2017 11:52 AM, D&R wrote:
> When I boot into the install there is an error in the destination section.
>
> I looked at the debug info in the storage.log and there was an
> error about sdb1 did not exist. But...
>
> When I reboot to F24 then ...
>
> cat /proc/mdstat
>
> md126 : active r
When I boot into the install there is an error in the destination section.
I looked at the debug info in the storage.log and there was an
error about sdb1 did not exist. But...
When I reboot to F24 then ...
cat /proc/mdstat
md126 : active raid1 sda2[2] sdb2[1]
961261568 blocks super 1.2 [
Hey peeps.
From a fed/centos cmdline...
pgrep -f "foo" | wc -l
will return 0 -- if "foo" doesn't exist in the procTBL, and something
else if "foo" is running.
The curiousity... When I have a simple php
$t isn't 0!! -- it's actually 1, or something else if foo is running..
Any ideas why?? I
On 08/09/2017 09:41 AM, ergodic wrote:
> Amen!
> Let me further add that neither Fedora 26 Live or Fedora 26 XFCE work.
> I had to install Fedora 25 and then upgrade with dnf to Fedora 26.
> Nautilus has become so limited that I switched to nemo.
Then you didn't do it correctly. F26 Xfce Live 64-b
On Wed, 2017-08-09 at 08:52 -0700, Thomas Dineen wrote:
> Gentle People:
>
>I hate to interrupt your Fedora 26 party, but well here goes a
> dose of reality from the
> USER's PROSPECTIVE!
Yours is not *the* user's perspective. Yours is *a* user's perspective.
Here is *my* user's perspective.
I have to get a new 500GB SSD card before installing on my old system,
so it will be a few more weeks.
I am assuming the OP is using GNOME. The Gnome g-ds are independent of
Fedora and Centos. I dropped Nautilus for Nemo back in Fedora 21. I
dropped Gnome for Xfce with F22. What a differen
On 08/09/2017 07:59 AM, mitchell@member.fsf.org wrote:
> Rick Stevens writes:
>
>>
>>
>> root@prophead ~]# strings /usr/sbin/grubby | grep "^/" | uniq
>> /lib64/ld-linux-x86-64.so.2
>> /boof
>> /dev
>> /boot/grub/menu.lst
>> /etc/grub2-efi.cfg
>> /boot/grub/grub.cfg
>> /etc/grub.d/
>> /boot/
Amen!
Let me further add that neither Fedora 26 Live or Fedora 26 XFCE work.
I had to install Fedora 25 and then upgrade with dnf to Fedora 26.
Nautilus has become so limited that I switched to nemo.
It is a shame!
- Original Message -
> Gentle People:
> I hate to interrupt your Fed
Gentle People:
I hate to interrupt your Fedora 26 party, but well here goes a dose
of reality from the
USER's PROSPECTIVE!
1) First of all F26's performance is very poor. its a CPU hog and DRAM !
I installed F26 in a Virtual Box (VBox)
on a two processor machine and it is so slow that it i
Rick Stevens writes:
>
>
> root@prophead ~]# strings /usr/sbin/grubby | grep "^/" | uniq
> /lib64/ld-linux-x86-64.so.2
> /boof
> /dev
> /boot/grub/menu.lst
> /etc/grub2-efi.cfg
> /boot/grub/grub.cfg
> /etc/grub.d/
> /boot/grub2/grubenv
> /etc/mtab
> /boot
> /etc/sysconfig/grub
> /proc/mdstat
>
30 matches
Mail list logo
