Re: Daemonologists wanted

Paul Johnson wrote: > David Liontooth wrote: > >> It might even be worth bugreporting the behavior that the sensor daemon >> fails if a probed sensor is absent, but I suspect that's a Debian issue, >> not an upstream sensors issue? > > Yes, reportbug would be the appropriate method to report thi

Re: Daemonologists wanted

David Liontooth wrote: > It might even be worth bugreporting the behavior that the sensor daemon > fails if a probed sensor is absent, but I suspect that's a Debian issue, > not an upstream sensors issue? Yes, reportbug would be the appropriate method to report this bug. -- To UNSUBSCRIBE, em

Re: Daemonologists wanted

Paul Johnson wrote: > For posterity, it might be helpful to post what motherboard and chipset > that's for. Right -- this is a Gigabyte K8NS Ultra-939. The Gigabyte K8NSC-939 has the same "AMD Athlon64/FX or Opteron temperature sensor", as does the Tyan Tomcat S8350 and lots of other amd64 boards

Re: Daemonologists wanted

David Liontooth wrote: > Paul Johnson wrote: > >> David Liontooth wrote: >> >>> >>> If I issue >>> >>> /etc/init.d/sensord start >>> >>> to start the sensor daemon, the script seems to run fine, but the daemon >>> doesn't actually start. On my other machines, it runs as expected. Any

Re: Daemonologists wanted

Paul Johnson wrote: > David Liontooth wrote: > >> >> If I issue >> >> /etc/init.d/sensord start >> >> to start the sensor daemon, the script seems to run fine, but the daemon >> doesn't actually start. On my other machines, it runs as expected. Any >> daemonologists out there? > > Wha

Re: Daemonologists wanted

David Liontooth wrote: > > If I issue > > /etc/init.d/sensord start > > to start the sensor daemon, the script seems to run fine, but the daemon > doesn't actually start. On my other machines, it runs as expected. Any > daemonologists out there? What's the .conf look like? Any log ent

Daemonologists wanted

If I issue /etc/init.d/sensord start to start the sensor daemon, the script seems to run fine, but the daemon doesn't actually start. On my other machines, it runs as expected. Any daemonologists out there? Dave #!/bin/sh -xv PATH=/bin:/usr/bin:/sbin:/usr/sbin + PATH=/bin:/usr/bin:/sb