Yeah, someone butterfingered epel-rpm-macros. The fixed package is in
epel-testing right now.
yum --enablerepo=epel-testing install epel-rpm-macros
See https://bugzilla.redhat.com/show_bug.cgi?id=1241655
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original
On 08/30/2015 12:02 PM, Mike Mohr wrote:
In my experience the mass market HBAs and RAID cards typically do support
only 8 or 16 drives. For the internal variety in a standard rack-mount
server you'll usually see either 2 or 4 iPass cables (each of which support
4 drives) connected to the
In my experience the mass market HBAs and RAID cards typically do support
only 8 or 16 drives. For the internal variety in a standard rack-mount
server you'll usually see either 2 or 4 iPass cables (each of which support
4 drives) connected to the backplane. The marketing material you've
Hi guys! Unfortunately there is no offtopic list but the subject
is somehow related to centos as the OS is/will be centos :)
So, under this thin cover i ask :
Is it possible that for a SAS controler like LSI 3008 that in specs
says that : This high-performance I/O controller supports T-10
data
When building packages in mock lately I see this a lot:
error: Macro %py2_install has unterminated body
Only started within last month, as far as I can tell the build actually
finishes just fine.
cause?
___
CentOS mailing list
CentOS@centos.org
On 8/30/2015 2:20 PM, Robert Nichols wrote:
Once the system gets into this state, the only remedy is a forced
power-off. What seems to be happening is that an NFS filesystem that
auto-mounted over a WiFi connection cannot be unmounted because the
WiFi connection is enabled only for my login and
On 08/30/2015 06:39 PM, Jason Warr wrote:
On 8/30/2015 4:59 AM, Adrian Sevcenco wrote:
On 08/30/2015 12:02 PM, Mike Mohr wrote:
such hardware, but expect the throughput to fall through the
floor if you use such hardware.
why? what is the difference between the silicon from a HBA card and
the
On 08/30/2015 04:20 PM, Robert Nichols wrote:
Once the system gets into this state, the only remedy is a forced
power-off. What seems to be happening is that an NFS filesystem that
auto-mounted over a WiFi connection cannot be unmounted because the
WiFi connection is enabled only for my login
On Sun, 30 Aug 2015 16:20:21 -0500
Robert Nichols wrote:
Once the system gets into this state, the only remedy is a forced
power-off. What seems to be happening is that an NFS filesystem that
auto-mounted over a WiFi connection cannot be unmounted because the
WiFi connection is enabled only
Once the system gets into this state, the only remedy is a forced
power-off. What seems to be happening is that an NFS filesystem that
auto-mounted over a WiFi connection cannot be unmounted because the
WiFi connection is enabled only for my login and gets torn down when
my UID is logged off.
On 8/30/2015 4:59 AM, Adrian Sevcenco wrote:
On 08/30/2015 12:02 PM, Mike Mohr wrote:
In my experience the mass market HBAs and RAID cards typically do support
only 8 or 16 drives. For the internal variety in a standard rack-mount
server you'll usually see either 2 or 4 iPass cables (each of
That is the thing - rpc.statd does have rpcbind a pre-req. It looks like
systemd is not handling this correctly. Just wondering if anyone knows a
good way to fix.
root@ls2 /usr/lib/systemd/system 110# grep Requires rpc-statd.service
Requires=nss-lookup.target rpcbind.target
On 8/30/15 7:45
* Hi, I am Martin, coming from the east of china, is a novice for
Linux. Kindly give me your advice. Thanks.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
On Sun, Aug 30, 2015 at 04:20:21PM -0500, Robert Nichols wrote:
Once the system gets into this state, the only remedy is a forced
power-off. What seems to be happening is that an NFS filesystem that
auto-mounted over a WiFi connection cannot be unmounted because the
WiFi connection is enabled
On 08/30/2015 04:45 PM, John R Pierce wrote:
On 8/30/2015 2:20 PM, Robert Nichols wrote:
Once the system gets into this state, the only remedy is a forced
power-off. What seems to be happening is that an NFS filesystem that
auto-mounted over a WiFi connection cannot be unmounted because the
I have seen some talk about this but have not seen any answers. I know
this is a problem on CentOS 7.1 and I also think it is a problem on
CentOS 7.0.
Basically if I have an NFS client only config - meaning that the
nfs-server.service is not enabled then I have to wait 60 seconds after
boot
On 08/31/2015 01:39 PM, Mark Selby wrote:
I have seen some talk about this but have not seen any answers. I know
this is a problem on CentOS 7.1 and I also think it is a problem on
CentOS 7.0.
Basically if I have an NFS client only config - meaning that the
nfs-server.service is not enabled
17 matches
Mail list logo
