whitivery <co55-s...@dea.spamcon.org> wrote:
>Jonathan Billings <billi...@negate.org>
>wrote:
>
>>On Sun, Dec 18, 2016 at 08:50:54PM -0800, whitivery wrote:
>>> It is a system with several servers (various platforms/distros).
>>>
>>
Jonathan Billings <billi...@negate.org>
wrote:
>On Sun, Dec 18, 2016 at 08:50:54PM -0800, whitivery wrote:
>> It is a system with several servers (various platforms/distros).
>>
>> One piece of software runs on all of the servers. For it to operate
>> corr
James Hogarth <james.hoga...@gmail.com>
wrote:
>On 18 Dec 2016 10:59, "whitivery" <co55-s...@dea.spamcon.org> wrote:
>
>Moving from CentOS 5 to CentOS 7, discovered that a test in a SysV
>initscript for whether it is running interactively, instead of at boo
Moving from CentOS 5 to CentOS 7, discovered that a test in a SysV
initscript for whether it is running interactively, instead of at boot
time, no longer works.
Under CentOS 7 / systemd, is there some way for the initscript to know
this?
___
CentOS
John R Pierce pie...@hogranch.com wrote:
On 11/16/2013 9:50 PM, whitivery wrote:
What else might I try?
centos 6.latest ?or at least 5.latest5.7 is circa 2011,
there's dozens of kernel patches since then, its up to 5.10 now.
Thank you John and John for the replies.
I was guessing
Using Core i7 boxes with CentOS 5.7, have experienced lockups on half of a
handful of units over a couple months. They are Logic Supply Mini-ITX
model KR960 with Core i7-3610QE.
A couple weeks ago I enabled self-reboot on kernel panic (echo 10
/proc/sys/kernel/panic) on all units, and had
Emmanuel Noobadmin centos.ad...@gmail.com
wrote:
On 10/13/11, whitivery co55-s...@dea.spamcon.org wrote:
Eth0 is the onboard device, using an updated VIA Velocity driver
(velocityget 1.42 instead of default via-velocity):
05:00.0 Ethernet controller: VIA Technologies, Inc. VT6120/VT6121/VT6122
whitivery co55-s...@dea.spamcon.org wrote:
Setting up bonding in active-backup mode 1 (using ARP monitoring)
on a server, it looked OK, but pulling the active link cable
didn't actually work, it didn't fail over.
Eventually with manual playing around with modprobe, ifconfig,
ifenslave, etc
Setting up bonding in active-backup mode 1 (using ARP monitoring)
on a server, it looked OK, but pulling the active link cable
didn't actually work, it didn't fail over.
Eventually with manual playing around with modprobe, ifconfig,
ifenslave, etc., a solution was stumbled upon: enslave the eth1
whitivery co55-s...@dea.spamcon.org wrote:
whitivery co55-s...@dea.spamcon.org wrote:
Patrick Lists
centos-l...@puzzled.xs4all.nl wrote:
On 03/10/2011 08:14 AM, whitivery wrote:
# This does not work
%include /tmp/drvdisk
# This works
#driverdisk
--source=nfs:10.0.4.157:/srv/cobbler
whitivery co55-s...@dea.spamcon.org wrote:
whitivery co55-s...@dea.spamcon.org wrote:
whitivery co55-s...@dea.spamcon.org wrote:
Patrick Lists
centos-l...@puzzled.xs4all.nl wrote:
On 03/10/2011 08:14 AM, whitivery wrote:
# This does not work
%include /tmp/drvdisk
# This works
#driverdisk
whitivery co55-s...@dea.spamcon.org wrote:
Patrick Lists
centos-l...@puzzled.xs4all.nl wrote:
On 03/10/2011 08:14 AM, whitivery wrote:
# This does not work
%include /tmp/drvdisk
# This works
#driverdisk
--source=nfs:10.0.4.157:/srv/cobbler/RHEL5.5_x86_402_409_410_DD.img
%packages
@base
Patrick Lists
centos-l...@puzzled.xs4all.nl wrote:
On 03/10/2011 08:14 AM, whitivery wrote:
# This does not work
%include /tmp/drvdisk
# This works
#driverdisk
--source=nfs:10.0.4.157:/srv/cobbler/RHEL5.5_x86_402_409_410_DD.img
%packages
@base
@core
%pre --erroronfail
echo
I've previously used includes in CentOS 4.4 and they worked fine.
But in CentOS 5.5, trying to specify a driver disk via an include
does not work.
If I instead specify it directly, it loads fine.
When it fails (because it can't see the disk drive - needs the
driver disk to see the hard disk),
14 matches
Mail list logo
