whitivery wrote:
>Jonathan Billings
>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
Jonathan Billings
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
>> correctly, the instance on one serve
James Hogarth
wrote:
>On 18 Dec 2016 10:59, "whitivery" 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 boot
>time, no longer works.
>
>Under CentOS 7 / systemd, is th
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 mai
John R Pierce 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 wa
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 anoth
Emmanuel Noobadmin
wrote:
>On 10/13/11, whitivery 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/VT6
whitivery 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,
>ife
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
d
whitivery wrote:
>whitivery wrote:
>
>>whitivery wrote:
>>
>>>Patrick Lists
>>> wrote:
>>>
>>>>On 03/10/2011 08:14 AM, whitivery wrote:
>>>>> # This does not work
>>>>> %include /tmp/drvdis
whitivery wrote:
>whitivery wrote:
>
>>Patrick Lists
>> wrote:
>>
>>>On 03/10/2011 08:14 AM, whitivery wrote:
>>>> # This does not work
>>>> %include /tmp/drvdisk
>>>>
>>>> # This works
>>
whitivery wrote:
>Patrick Lists
> 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/RHE
Patrick Lists
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
>>
>>
>> %packa
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), in
14 matches
Mail list logo
