Displaying 5 results from an estimated 5 matches for "02.18".
Did you mean:
0.18
2018 Jan 12
3
lshw in centos 7
Folks
I've been running lshw for years in both Centos 6 and Centos 7, yet
just recently it started hanging. Neither a Control^C nor a "kill"
of the process cured the hang; only a reboot.
When I run it by hand from the command line, it displays stuff on the
next line overwriting it with things like PCI, USB. And USB is the
last thing I see. A Control-C does not unlock it.
I
2009 Jun 03
11
Centos 5.3 -> Apache - Under Attack ? Oh hell....
Guys, apache cpus usage is hitting 100% sometimes ( to such an extent that its very noticeable) on a box with just 8 users or so.
i m getting this when i run 'top'. The worrying thing is seeing the work 'atack' under command
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
23119 apache 15 0 964 556 472 S 0.7 0.0 0:03.68 atack
23479 apache 15
2018 Jan 12
0
lshw in centos 7
On 11 January 2018 at 20:23, david <david at daku.org> wrote:
> Folks
>
> I've been running lshw for years in both Centos 6 and Centos 7, yet just
> recently it started hanging. Neither a Control^C nor a "kill" of the
> process cured the hang; only a reboot.
>
Is this just one system or a range of boxes? I just ran it on 2
different ones running CentOS 7 and
2010 Jan 31
1
How to split data frame into groups by a list of factors?
Dear R users:
I am dealing a data frame x as followings:
Date trade_day IV.b IV.a
1 2003-03-02 19 0.1724818 0.1815687
2 2003-03-02 18 0.1733542 0.1763827
3 2003-03-02 19 0.1753308 0.1783653
4 2003-03-03 16 0.1751217 0.1781624
5 2003-03-03 16 0.1738580 0.1768961
6 2003-03-03 19 0.1733346 0.1763800
......
I want to split the data flame
2018 Jan 12
3
lshw in centos 7 withdrawn
John--
Thanks for the suggestion. I finally had a chance to get to the
system in question, It was the only one of many that exhibited the
USB hang. I tried a reboot with the two USB disks
disconnected. Everything worked. I plugged them in, and then did
both "lsusb -v" and "lshw", and again, everything worked.
Continuing my test:
Reboot with both drives plugged in: