search for: sy1t

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?

On 18 Dec 2016 10:59, "whitivery" <co55-sy1t at 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 boot time, no longer works. Under CentOS 7 / systemd, is there some way for the initscript to know this? Generally "interactive...

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 Console 2 I can see that /tmp/drvdisk exists and has the line I wrote to it. I see nothing

Jonathan Billings <billings at 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 >> correctly, the instance on one server (prime) must start before the others >> (auxiliary). >>

James Hogarth <james.hogarth at gmail.com> wrote: >On 18 Dec 2016 10:59, "whitivery" <co55-sy1t at 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 boot >time, no longer works. > >Under CentOS 7 / systemd, is there some way for the initscript to know >this? &...

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 device before eth0, and all is good. Why this should matter is a puzzle - I could not find

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 another unit lock up rather than reboot itself. I'm not sure how to pursue the problem. Doing