Displaying 2 results from an estimated 2 matches for "broken_driv".
Did you mean:
broken_driver
2008 Nov 19
1
[nut-commits] svn commit r1556 - in trunk: . docs drivers scripts/hal scripts/hotplug scripts/udev tools
...nk/ChangeLog
> trunk/Makefile.am
> trunk/configure.in
> trunk/docs/new-drivers.txt
> trunk/drivers/ (props changed)
> trunk/drivers/Makefile.am
[snip]
I noticed in the Makefile.am you flagged this driver as broken. What
is the reason for not flagging the driver itself 'broken_driver = 1'
as well, so that people that still use it will be warned why it
doesn't work anymore by the time we release nut-2.4?
Looking at the comments in the driver about the problems with 2.6.x
kernels I wouldn't be too heartbroken if we would drop it from the
stable tree by the...
2005 Oct 23
0
FC4 + nut => shutdown sequence conundrum
...fatal("Can't chdir to %s", dflt_statepath());
setup_signals();
/* clear out callback handler data */
memset(&upsh, '\0', sizeof(upsh));
upsdrv_initups();
/* now see if things are very wrong out there */
if (broken_driver) {
printf("Fatal error: broken driver. It probably needs to
be con\verted.\n");
printf("Search for 'broken_driver = 1' in the source for
more d\etails.\n");
exit(EXIT_FAILURE);
}
if (do_forceshutdown)...