[Nut-upsuser] tripplite_usb/nut-2.2.1: Driver not connected.
forest at alittletooquiet.net
Thu May 29 18:05:36 UTC 2008
On Thu, May 29, 2008 at 02:01:39PM -0400, Charles Lepple wrote:
> On Thu, May 29, 2008 at 1:00 PM, Forest Bond <forest at alittletooquiet.net> wrote:
> > Next, I tried to generate a plain old core file with:
> > # ulimit -c 50000
> > # /lib/nut/tripplite_usb -a tripplite -DDD
> > I still get the segfault, but I can't seem to generate a core file. Would there
> > be something funny about this issue that would prevent me from getting a core
> > dump? I don't know much about these things, to be honest, but I'd love to help
> > debug.
> Not sure why it won't generate a core file, although it may have
> something to do with switching userids. Can the 'nut' system user
> write to the directory where you started the driver? Did it put the
> file in one of the NUT system directories? (/var/lib/nut,
> /var/run/nut, etc.)
I'll poke around.
> Arjen pointed out what is the most likely cause of the segfault (our
> reconnection code has changed a bit since the driver was first
> written), but the problem is that I won't have time to work on that
> for a week or so.
Would it behoove me to downgrade nut?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20080529/28c45341/attachment.pgp
More information about the Nut-upsuser