2009/8/10 Charles Lepple
> On Aug 10, 2009, at 5:00 AM, Arnaud Quette wrote:
>
> "Can't claim the device" even if I run as root
>>
>> iirc, there was no detach_device() primitive outside of linux.
>>
>
> In older versions of Mac OS X (either 10.3 or 10.4) you could ignore the
> return code when
On Aug 10, 2009, at 5:00 AM, Arnaud Quette wrote:
"Can't claim the device" even if I run as root
iirc, there was no detach_device() primitive outside of linux.
In older versions of Mac OS X (either 10.3 or 10.4) you could ignore
the return code when claiming the device, and the two processe
On Aug 10, 2009, at 2:00 AM, Christian Huldt wrote:
I'm not sure of the consequences of removing disabling ioupsd, but I
would expect it to be restored by software updates at an
unpredictable rate...
There should be a way to disable it. I'm looking into it.
2009/8/10 Christian Huldt
>
> Christian Huldt
> christ...@solvare.se
> +46704612207
>
>
>
> 9 aug 2009 kl. 21.55 skrev Charles Lepple:
>
> On Aug 9, 2009, at 9:25 AM, Christian Huldt wrote:
>>
>> Is there some smart way of not having ioupsd claming the device on mac os
>>> x?
>>>
>>
>> My only
Christian Huldt
christ...@solvare.se
+46704612207
9 aug 2009 kl. 21.55 skrev Charles Lepple:
On Aug 9, 2009, at 9:25 AM, Christian Huldt wrote:
Is there some smart way of not having ioupsd claming the device on
mac os x?
My only working Macs (at the moment) are laptops, so I haven't had
On Aug 9, 2009, at 9:25 AM, Christian Huldt wrote:
Is there some smart way of not having ioupsd claming the device on
mac os x?
My only working Macs (at the moment) are laptops, so I haven't had to
try this in a while. What errors do you get if you just try to run
usbhid-ups?
Or having
Is there some smart way of not having ioupsd claming the device on mac
os x?
Or having nut talk to ioupsd?
(/usr/ibexec/ioupsd is the builtin ups daemon, but I need the machine
to tell the other machine about the UPS status, and ioupsd does not do
networking AFAIK...)
Christian Huldt
chri
On 4/2/06, Ted Bardusch <[EMAIL PROTECTED]> wrote:
> I've got 2.0.3 running on my XServe under 10.4.5, but I had to put a
> serial adapter on the USB port instead of using a direct USB
> connection. With the direct USB connection, the OS X native UPS
> solution took precedence.
>
> Anyone know how
I've got 2.0.3 running on my XServe under 10.4.5, but I had to put a
serial adapter on the USB port instead of using a direct USB
connection. With the direct USB connection, the OS X native UPS
solution took precedence.
Anyone know how to prevent the OS X UPS handler from taking over on a
On 3/15/06, Jason Ferrara <[EMAIL PROTECTED]> wrote:
> I'm not currently using a StartupItem, but I could.
Are you starting it from the rc file?
> But then the question is how do I make sure that at shutdown time its the
> last StartupItem to get run, and that when it is run the filesystems are
Original Message-
From: "Charles Lepple" <[EMAIL PROTECTED]>
To: "Jason Ferrara" <[EMAIL PROTECTED]>
Cc: nut-upsuser@lists.alioth.debian.org
Sent: 3/10/06 10:58 AM
Subject: Re: [Nut-upsuser] nut on Mac OS X. Where to put upsdrvctl shutdown?
On 3/9/06, Jason Fer
On 3/9/06, Jason Ferrara <[EMAIL PROTECTED]> wrote:
> I've installed nut on a Mac OS X machine (XServe running Mac OS X
> 10.3.9). It all seems to work fine except.
>
> I can't figure out where to put the upsdrvctl shutdown command in
> order to get the ups to cut power after the computer shuts
I've installed nut on a Mac OS X machine (XServe running Mac OS X
10.3.9). It all seems to work fine except.
I can't figure out where to put the upsdrvctl shutdown command in
order to get the ups to cut power after the computer shuts down.
There doesn't seem to be any sort of script tha
13 matches
Mail list logo
