|
ok
On Wed, Jul 31, 2013 at 7:32 AM, <rob@xxxxxxxxx> wrote:
Native. Originally it was guested. There was much wailing and gnashingminutes.
of teeth by the consultants saying that caused this issue and that issue.
So we've unloaded and reloaded to dedicated. If I had known the linux
advocates (duh! why don't I ask him?) then that I knew now I would have
had a loaded gun to deal with the consultants.
As it is, said consultant says he'll just kick up the timer to 20
native
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Jack Kingsley <iseriesflorida@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 07/31/2013 05:48 AM
Subject: Re: What is the suse linux equivalent of QUPSDLYTIM?
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Rob are you running your lpar of linux as a virtual lpar to I, or a
LPAR using power linux.bit
On Tue, Jul 30, 2013 at 6:56 PM, Clay B Carley <cbc@xxxxxxxxx> wrote:
I've had some more coffee and thought about your original question a
portmore in depth.
I would start with:
chkconfig --list
To see what services are there (running or not), to get an idea of what
might be running. If there is a "service" that monitors the serial
usesfor UPS activity, it may be listed there.
I'd also take a look at the entire output of:
ps -aux
Or even
ps -auxwww
To see what is actually running, and hopefully to see what is watching
for UPS activity as well.
Being more of a Red Hat/ CentOS guy, I'm not sure what SUSE offers out
of the box for UPS activity; but I would imagine that unless this is
some custom users "server", the default package/ software that SUSE
listshould be what you find.list
Good luck,
Clay Carley
rob@xxxxxxxxx wrote:
Based on what I do not have running I suspect NUT is not running.--
Rob Berendt
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.