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
>>> daemonologists out there?
>> What's the .conf look like? Any log entries after you try starting
> But you're right - the syslog shows the failure:
> Dec 20 10:36:14 chianti sensord: sensord started
> Dec 20 10:36:14 chianti sensord: Chip: k8temp-pci-00c3
> Dec 20 10:36:14 chianti sensord: Adapter: PCI adapter
> Dec 20 10:36:14 chianti sensord: Mboard: 31.00
> Dec 20 10:36:14 chianti sensord: Error getting sensor data: k8temp/temp2:
> Can't access procfs/sysfs file
> Dec 20 10:36:14 chianti sensord: sensord failed
> It turns out the solution was to add a couple of ignores to the
> configuration (previous conf below):
> chip "k8temp-*"
> label temp1 "Mboard"
> ignore temp2
> label temp3 "CPU k8"
> ignore temp4
> The error messages are not very helpful to newbies -- now I realize
> that "Can't access procfs/sysfs file" means "there isn't any temp2 sensors
> according to /proc or /sys, so I'm going to fail".
The errors aren't particularly helpful if you don't have an intimate
knowledge of I2C in general, I'm afraid. I have similar problems
configuring sensord for a new system myself.
> A newbie like myself
> might think sensors isn't seeing /proc or /sys, or that these file systems
> aren't correctly installed, and so on. In any case, the default behavior
> shouldn't be to fail because some ignore statements are missing!
> Thanks for your help -- that's really all I needed, and hopefully this
> will be useful for someone else.
For posterity, it might be helpful to post what motherboard and chipset