> I am working on setting up sensorsd so that i can automatically turn on
> > my display when docking my laptop, but on doing so sensorsd does not
> > execute my shell script. In syslogd sensord shows the sensors being
> > tripped so i am confused on why the shell script wil
On 2019-07-25, cheddar-cheeze wrote:
> I am working on setting up sensorsd so that i can automatically turn on
> my display when docking my laptop, but on doing so sensorsd does not
> execute my shell script. In syslogd sensord shows the sensors being
> tripped so i am confused on w
I am working on setting up sensorsd so that i can automatically turn on
my display when docking my laptop, but on doing so sensorsd does not
execute my shell script. In syslogd sensord shows the sensors being
tripped so i am confused on why the shell script will no execute.
#/etc/sensorsd.conf
; welcome. This is my config: /etc/sensorsd.conf:
> >
> > acpiac0.indicator0:command=/etc/sensorsd/ac_power %2
>
> I am using:
>
> hw.sensors.acpiac0.indicator0:low=1:command=/etc/sensorsd/acpiac %2 %3 %4
>
> The "%3 %4" is just useful for debugging, y
piac0.indicator0:command=/etc/sensorsd/ac_power %2
I am using:
hw.sensors.acpiac0.indicator0:low=1:command=/etc/sensorsd/acpiac %2 %3 %4
The "%3 %4" is just useful for debugging, you don't need it.
But are you sure you can omit "hw.sensors."?
The sensorsd.conf(5) m
Hi all,
I'm tweaking how my laptop behaves depending on whether it is pluggde
into AC or not. Any hints or alternative suggestions are welcome.
This is my config:
/etc/sensorsd.conf:
acpiac0.indicator0:command=/etc/sensorsd/ac_power %2
and this is the script:
#!/bin/sh
echo $1
es between On/Off with a user limit of
`low=0:high=0` should definitely be triggered as reported by the
prior users (http://marc.info/?l=openbsd-misc=144526769005460=2).
http://BXR.SU/OpenBSD/usr.sbin/sensorsd/sensorsd.c#check_sdlim
370if (sensor.flags & SENSOR_FINVALID)
371
I've tried to change low=1:high=2 to low=0:high=0
but I haven't got *Off* current state for this sensor from sensord:
- hw.sensors.upd0.indicator2=On (ACPresent), OK
Even for AC disconnected sensord repors that ACPresent is *On*,
however when I look for
- sysctl hw.sensors.upd0.indicator2
it
:59:27 gw sensorsd[2261]: upd0.percent1: 0.00%, UNKNOWN
Feb 25 13:45:43 gw sensorsd[13167]: upd0.percent1: 0.00%, UNKNOWN
On Wed, Feb 24, 2016 at 3:38 AM, lilit-aibolit <lilit-aibo...@mail.ru> wrote:
> On 03/22/2015 05:44 PM, T. Ribbrock wrote:
>>
>> Then, I re-applied power, but that, too, was never flagged by sensorsd.
>> For some reason, it looks like sensorsd only ever detects a status
On 03/22/2015 05:44 PM, T. Ribbrock wrote:
Then, I re-applied power, but that, too, was never flagged by
sensorsd. For some reason, it looks like sensorsd only ever detects a
status change (for these rules) when it gets started - but not
afterwards. Regards, Thomas
Have you succeed
ues to OK /
> WARN / CRITICAL status. Currently any value successfully read is
> marked OK.
>
> I'm working with tech@ and slowly writing diffs to improve these things.
>
> --david
Resurrecting an old thread since I just ran into the same problem in
5.8. To summarize, upd(4) expose
d of. The high/low difference is what values you consider "within"
> > normal operating parameters (and the output of %l). The upd(4) code
> > hasn't yet been taught how to map specific indicator values to OK /
> > WARN / CRITICAL status. Currently any value
you consider "within"
>> > normal operating parameters (and the output of %l). The upd(4) code
>> > hasn't yet been taught how to map specific indicator values to OK /
>> > WARN / CRITICAL status. Currently any value successfully read is
>> > marked OK.
>>
On 19 October 2015 at 11:31, David Higgs <hig...@gmail.com> wrote:
> On Mon, Oct 19, 2015 at 11:11 AM, Maxim Khitrov <m...@mxcrypt.com> wrote:
>> Also, upd always sets sensor status to "OK," so sensorsd never
>> triggers commands for status changes; we
Hi all,
one of the remaining kinks in the cable that still need working out
after me updating to OpenBSD 5.6 is the fact that I can no longer use
apcupsd to monitor the APC Back-UPS CS 500 that is connected to the
server via USB. From what I have gathered so far, one has to use
sensorsd instead
On Sun, Mar 22, 2015 at 03:26:30PM +, Stuart Henderson wrote:
On 2015-03-22, T. Ribbrock emga...@gmx.net wrote:
What I cannot seem to get to work is that sensorsd *reacts* to these
changes. Based on the examples in the thread mentioned above, I've
created a small script /etc/sensorsd
On 2015-03-22, T. Ribbrock emga...@gmx.net wrote:
What I cannot seem to get to work is that sensorsd *reacts* to these
changes. Based on the examples in the thread mentioned above, I've
created a small script /etc/sensorsd/upd.sh that looks as follows:
# cat /etc/sensorsd/upd.sh
echo
I use low=1:high=2, I get On for %3 (low limit) as well
as for %4 (high limit)
- Reading sensorsd.conf(5):
If the limits are crossed or if the status provided by the driver
changes, sensorsd(8)'s alert functionality is triggered and a command,
if specified, is executed
If limits
On Mon, Dec 8, 2014 at 11:47 AM, David Higgs hig...@gmail.com wrote:
sysctl(8) will display Off if the value is zero, and On for nonzero.
So, using the closed interval rule above, you should use high=0
for indicators that you consider in good state when Off (i.e.
ShutdownImminent), and low=1
On Mon, Dec 8, 2014 at 3:23 PM, trondd tro...@gmail.com wrote:
On Mon, Dec 8, 2014 at 11:47 AM, David Higgs hig...@gmail.com wrote:
sysctl(8) will display Off if the value is zero, and On for nonzero.
So, using the closed interval rule above, you should use high=0
for indicators that you
On Mon, Dec 8, 2014 at 3:37 PM, trondd tro...@gmail.com wrote:
On Mon, Dec 8, 2014 at 3:23 PM, trondd tro...@gmail.com wrote:
On Mon, Dec 8, 2014 at 11:47 AM, David Higgs hig...@gmail.com wrote:
sysctl(8) will display Off if the value is zero, and On for nonzero.
So, using the closed
On Mon, Dec 8, 2014 at 3:45 PM, David Higgs hig...@gmail.com wrote:
I'm working with tech@ and slowly writing diffs to improve these things.
--david
I saw that. Thanks!
Tim.
hig...@gmail.com (David Higgs), 2014.11.28 (Fri) 15:43 (CET):
On Fri, Nov 28, 2014 at 2:45 AM, Marcus MERIGHI mcmer-open...@tor.at wrote:
What I have now:
$ getcap -a -f /etc/sensorsd.conf
hw.sensors.upd0.indicator0:low=1:high=2:command=/etc/sensorsd/upd.sh \
%l %n %s %x %t %2 %3 %4
)
- Reading sensorsd.conf(5):
If the limits are crossed or if the status provided by the driver
changes, sensorsd(8)'s alert functionality is triggered and a command,
if specified, is executed
If limits are crossed, yes; if status changes, no, unless you use the
low=1:high=2 trick.
- Reading
On Fri, Nov 28, 2014 at 2:45 AM, Marcus MERIGHI mcmer-open...@tor.at wrote:
What I have now:
$ getcap -a -f /etc/sensorsd.conf
hw.sensors.upd0.indicator0:low=1:high=2:command=/etc/sensorsd/upd.sh \
%l %n %s %x %t %2 %3 %4
hw.sensors.upd0.indicator1:low=1:high=2:command=/etc/sensorsd/upd.sh
-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of
David Higgs
Sent: Friday, November 28, 2014 9:43 AM
To: misc@openbsd.org
Subject: Re: sensorsd, upd, and state changes
Do you mind saying what type of USB you have, and what these sensors map
are for your hardware?
I have
On Fri, November 28, 2014 2:45 am, Marcus MERIGHI wrote:
j...@entropicblur.com (Joe Gidi), 2014.11.27 (Thu) 16:41 (CET):
I just spent some more time poking at this and I'm still unable to get
So did I...
sensorsd to recognize upd state changes. This is a bit of a frustrating
regression from
On Fri, November 28, 2014 9:43 am, David Higgs wrote:
On Fri, Nov 28, 2014 at 2:45 AM, Marcus MERIGHI mcmer-open...@tor.at
wrote:
What I have now:
$ getcap -a -f /etc/sensorsd.conf
hw.sensors.upd0.indicator0:low=1:high=2:command=/etc/sensorsd/upd.sh \
%l %n %s %x %t %2 %3 %4
I just spent some more time poking at this and I'm still unable to get
sensorsd to recognize upd state changes. This is a bit of a frustrating
regression from my point of view, since I can no longer use apcupsd unless
I disable uhidev in the kernel.
Does anyone have a working example
j...@entropicblur.com (Joe Gidi), 2014.11.27 (Thu) 16:41 (CET):
I just spent some more time poking at this and I'm still unable to get
So did I...
sensorsd to recognize upd state changes. This is a bit of a frustrating
regression from my point of view, since I can no longer use apcupsd unless
. Now, I'd like to configure sensorsd to monitor the device
and invoke a script when the power goes out. I have this line in
sensorsd.conf:
hw.sensors.upd0.indicator2:command=/etc/sensorsd/ups.sh %s %2
The ups.sh script currently just echoes the token values that it's passed
to a log file
Hi Marcus,
Thanks for the reply. Unfortunately, the low=1:high=2 doesn't seem to
work for indicator2. When I start sensorsd I see an initial event logged
as the status goes from undefined to OK, but no further events as I
unplug/plug the UPS. I tried monitoring indicator0 as in the Undeadly
Just after I sent this, I happened to notice these lines in
/var/log/messages. These came from the tests with the low=1:high=2
attributes set in sensorsd.conf per the Undeadly example.
Nov 23 10:58:08 microserver sensorsd[6250]: upd0.indicator2: exceeds
limits: On is below On
Nov 23 10:59:54
j...@entropicblur.com (Joe Gidi), 2014.11.23 (Sun) 17:19 (CET):
Just after I sent this, I happened to notice these lines in
/var/log/messages. These came from the tests with the low=1:high=2
attributes set in sensorsd.conf per the Undeadly example.
Nov 23 10:58:08 microserver sensorsd[6250
the Undeadly example.
Nov 23 10:58:08 microserver sensorsd[6250]: upd0.indicator2: exceeds
limits: On is below On
Nov 23 10:59:54 microserver sensorsd[12047]: upd0.indicator2: exceeds
limits: On is below On
Nov 23 11:07:00 microserver sensorsd[27413]: upd0.indicator0: exceeds
limits: On is below
hw.sensors.upd0.indicator3=On (BatteryPresent), OK
hw.sensors.upd0.indicator4=Off (ShutdownImminent), OK
hw.sensors.upd0.percent0=79.00% (RemainingCapacity), OK
hw.sensors.upd0.percent1=100.00% (FullChargeCapacity), OK
So far, so good. Now, I'd like to configure sensorsd to monitor the device
and invoke a script
Hello,
I'm trying to use sensorsd to shutdown my Thinkpad T410 laptop when
the battery reaches the low capacity level. However, when I add the
line shown below to sensorsd.conf the laptop always shutdown within a
couple of minutes of booting regardless of the current battery level
or if running
laurence.rochf...@gmail.com wrote:
Hello,
I'm trying to use sensorsd to shutdown my Thinkpad T410 laptop when
the battery reaches the low capacity level. However, when I add the
line shown below to sensorsd.conf the laptop always shutdown within a
couple of minutes of booting regardless of the current
Delay can be due to a limitations of sensorsd(8):
CAVEATS
Certain sensors may flip status from time to time. To guard against
false reports, sensorsd implements a state dumping mechanism. However,
this inevitably introduces an additional delay in status reporting and
command
Hello.
I'm not a proficient shell script writer, so I would like advice
and criticism for my sensorsd(8) temperature script.
In particular, I would like the above email to root to include helpful
information that would help explain why the temperature went to critical.
Anything else that I may
On Sat, Jun 16, 2012 at 10:24:02PM -0700, Robert Connolly wrote:
Hello.
The acpiac(4) man page mentions that the AC power source status can be
monitored by sensorsd(8), but sensorsd(8) does not monitor this sensor as
far as I know. apmd(8) does however.
Could the acpiac(4) man page
Hello.
The acpiac(4) man page mentions that the AC power source status can be
monitored by sensorsd(8), but sensorsd(8) does not monitor this sensor as
far as I know. apmd(8) does however.
Could the acpiac(4) man page be reworded to reflect this?
Thanks
Hello.
I have some problems with the tokens used in sensorsd.conf.
From /etc/sensorsd.conf (it's set to 51C for testing purposes):
hw.sensors.km0.temp0:high=51C:command=/etc/sensorsd/cpu-temp.sh %l %x %t %2
%3 %4
hw.sensors.acpitz0.temp0:high=75C:command=/etc/sensorsd/cpu-temp.sh %l %x
%t %2 %3
On 2012-06-08, Robert Connolly robertconnolly1...@gmail.com wrote:
From /etc/sensorsd.conf (it's set to 51C for testing purposes):
hw.sensors.km0.temp0:high=51C:command=/etc/sensorsd/cpu-temp.sh %l %x %t %2
%3 %4
Looks like a shell problem not a sensorsd one; I guess you probably
want some
thing from
sensorsd -- thanks for shedding light on what's going on. I'll use a shell
script command on watthour3 to check the other vals through sysctl directly,
as you suggest.
I wish that hw.sensors.acpibat0.raw0 changed state from OK to something else
when it was discharging. I wonder why
Hi,
I'm configuring sensorsd to conditionally shutdown -- based on Wh of charge
left in laptop battery and whether or not the computer is plugged in -- and
it seems that sensorsd might have a bit of a blind spot when it comes my
available sensors. After reporting the initial states, no more
On 14 November 2010 13:03, mark hellewell mark.hellew...@gmail.com wrote:
Hi,
I'm configuring sensorsd to conditionally shutdown -- based on Wh of charge
left in laptop battery and whether or not the computer is plugged in -- and
it seems that sensorsd might have a bit of a blind spot when
Hi all,
I set sensorsd and sensorsd.conf this way :
# $OpenBSD: sensorsd.conf,v 1.8 2007/08/14 19:02:02 cnst Exp $
#
# Sample sensorsd.conf file. See sensorsd.conf(5) for details.
#
# +5 voltage (volts)
#hw.sensors.lm0.volt3:low=4.8V:high=5.2V
# +12 voltage (volts)
#hw.sensors.lm0.volt4:low
On Sat, Mar 06, 2010 at 02:26:28PM +0100, Tomas Bodzar wrote:
Hi all,
I set sensorsd and sensorsd.conf this way :
# $OpenBSD: sensorsd.conf,v 1.8 2007/08/14 19:02:02 cnst Exp $
# Monitor laptop battery for remaining capacity
hw.sensors.acpibat0.watthour3:low=1.40Wh:command=/etc/sensorsd
Thx. I will prepare some more complicated creatures :-)
On Sat, Mar 6, 2010 at 5:09 PM, Joachim Schipper
joac...@joachimschipper.nl wrote:
On Sat, Mar 06, 2010 at 02:26:28PM +0100, Tomas Bodzar wrote:
Hi all,
I set sensorsd and sensorsd.conf this way :
# $OpenBSD: sensorsd.conf,v 1.8 2007
On 6 March 2010 08:26, Tomas Bodzar tomas.bod...@gmail.com wrote:
Hi all,
I set sensorsd and sensorsd.conf this way :
# $OpenBSD: sensorsd.conf,v 1.8 2007/08/14 19:02:02 cnst Exp $
#
# Sample sensorsd.conf file. See sensorsd.conf(5) for details.
#
# +5 voltage (volts)
#hw.sensors.lm0
I decided to use sensorsd for the first time and am a little confused as
to why it thinks I only have two (2) sensors when I have asked it to
watch
four (4) items. Any ideas would be great.
The output from sysctl hw is the following
hw.disknames=sd0,cd0
hw.diskcount=2
hw.sensors.cpu0.temp0=34.00
I decided to use sensorsd for the first time and am a little confused as
to why it thinks I only have two (2) sensors when I have asked it to
watch
four (4) items. Any ideas would be great.
The output from sysctl hw is the following
hw.disknames=sd0,cd0
hw.diskcount=2
hw.sensors.cpu0
-Original Message-
From: Theo de Raadt [mailto:dera...@cvs.openbsd.org]
Sent: Wednesday, January 06, 2010 3:45 PM
To: Morris, Roy
Cc: misc@openbsd.org
Subject: Re: Sensorsd
I decided to use sensorsd for the first time and am a little confused
as
to why it thinks I only have two (2
2010/1/6, Morris, Roy rmor...@internetsecure.com:
Ok, figured that might be what it was! Thanks. Too bad it
would be nice to know if the disk count changed ie. someone
plugged in a USB key.
You can use hotplugd(8) for that.
-Original Message-
From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of
Alexander Polakov
Sent: Wednesday, January 06, 2010 4:11 PM
To: misc@openbsd.org
Subject: Re: Sensorsd
2010/1/6, Morris, Roy rmor...@internetsecure.com:
Ok, figured that might be what
Constantine A. Murenin wrote:
On 27/07/2009, Federico Giannici giann...@neomedia.it wrote:
I'm using for the first time sensorsd to monitor RAID controller status and
motherboard temperature. A script of mine is called that sends me an email.
System is OpenBSD 4.4 amd64.
The problem
I'm using for the first time sensorsd to monitor RAID controller status
and motherboard temperature. A script of mine is called that sends me an
email. System is OpenBSD 4.4 amd64.
The problem is the value of the %2 %3 and %4 tokens passed as arguments
to the command. I thought
On 27/07/2009, Federico Giannici giann...@neomedia.it wrote:
I'm using for the first time sensorsd to monitor RAID controller status and
motherboard temperature. A script of mine is called that sends me an email.
System is OpenBSD 4.4 amd64.
The problem is the value of the %2 %3 and %4
Hi Misc,
I put the following line in my sensorsd.conf file:
hw.sensors.acpibat0.raw0:command=/etc/sensorsd/bat_status %2
When the battery's laptop status change, bat_status program is
executed using param %2 (sensor's value can be: 0 when battery is
idle, 1 when battery is discharging and 2
On Wednesdayen den 4 July 2007 04.17.30 you wrote:
On 03/07/07, Per-Olov Sjvholm [EMAIL PROTECTED] wrote:
Hi Misc
I am probably missing something, but what..
sensorsd says in the syslog that the sensor is within limits even
though a sysctl -a|grep sensor shows
values specified (that otherwise will be ignored)
and simply trigger on status transitions.
In other words, for those sensors that provide the status themselves,
the keywords high and low in sensorsd.conf have no effect. This
limitation was removed at c2k7 [1], and the newest sensorsd in OpenBSD
On 03/07/07, Per-Olov Sjvholm [EMAIL PROTECTED] wrote:
Hi Misc
I am probably missing something, but what..
sensorsd says in the syslog that the sensor is within limits even though
a sysctl -a|grep sensor shows that it is not.
Are there any known bugs? I have checked the list and cannot
Hi Misc
I am probably missing something, but what..
sensorsd says in the syslog that the sensor is within limits even though
a sysctl -a|grep sensor shows that it is not.
Are there any known bugs? I have checked the list and cannot find anything
related to this... I run a Dell PE830
Hello,
Last update (~2 weeks ago) and the one from last night result in
sensorsd shutting down my PC within 2 to 4 minutes after booting up.
Now /etc/sensorsd.conf has an entry in it that I added to safely
shut the computer down if the CPU gets too hot. The only problem is
that sensorsd keeps
On 27/05/07, Steven [EMAIL PROTECTED] wrote:
Hello,
Last update (~2 weeks ago) and the one from last night result in
sensorsd shutting down my PC within 2 to 4 minutes after booting up.
Now /etc/sensorsd.conf has an entry in it that I added to safely
shut the computer down if the CPU gets too
In /etc/sensorsd.conf
hw.sensors.3:low=4.8V:high=5.2V:command=/bin/sh /etc/sensorsd/notify
In /etc/sensorsd/notify
#!/bin/sh
/usr/bin/tail -n 25 /var/log/daemon | /usr/bin/grep sensorsd | /usr/
bin/grep exceed /etc/sensorsd/`date +%m%d%y_%H%M`.log
/usr/bin/mail -s Hardware Sensors Monitor
On 24/03/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
In /etc/sensorsd.conf
hw.sensors.3:low=4.8V:high=5.2V:command=/bin/sh /etc/sensorsd/notify
In /etc/sensorsd/notify
#!/bin/sh
/usr/bin/tail -n 25 /var/log/daemon | /usr/bin/grep sensorsd | /usr/
bin/grep exceed /etc/sensorsd/`date +%m%d
didn't post the whole sensorsd.conf
hw.sensors.3:low=4.8V:high=5.2V:command=/bin/sh /etc/sensorsd/notify
# +12 voltage (volts)
hw.sensors.4:low=11.5V:high=12.55V
# Chipset temperature (degrees Celsius)
hw.sensors.7:high=35C
hw.sensors.9:low=3000
hw.sensors.10:low=3000
(hw.sensors.3 in conf,
hw.sensors.4 on log).
Sorry I didn't post the whole sensorsd.conf
hw.sensors.3:low=4.8V:high=5.2V:command=/bin/sh /etc/sensorsd/notify
# +12 voltage (volts)
hw.sensors.4:low=11.5V:high=12.55V
You do not have a command specified on hw.sensors.4, so you should
On Mar 24, 2007, at 5:27 PM, Constantine A. Murenin wrote:
You do not have a command specified on hw.sensors.4, so you should not
be expecting any emails to be sent when this sensor undergoes
transitions from one state to another.
I think the syntax of sensorsd.conf is rather obvious here --
values specified (that otherwise will be ignored)
and simply trigger on status transitions.
However, volt0 and volt1 on acpibat never change status from an OK,
so they will never be triggered in sensorsd, which may or may not be
desirable behaviour.
The following patch will allow you to set
.volt1
hw.sensors.acpibat0.volt1=7.96 VDC (current voltage), OK
$ tail -3 /etc/sensorsd.conf
hw.sensors.acpibat0.volt1:low=8V:high=9V
no matter what I set, sensorsd always says within limits.
sensorsd.conf(5) says [that's how it is supposed to work]
The following patch will allow you to set
.volt1=7.96 VDC (current voltage), OK
$ tail -3 /etc/sensorsd.conf
hw.sensors.acpibat0.volt1:low=8V:high=9V
#:command=/etc/sensorsd/shutdown %2 %3
$ sudo sensorsd -d
^C
$ tail -1 /var/log/messages
Jan 12 18:25:24 trin sensorsd[15369]: hw.sensors.acpibat0.volt1: within limits,
value: 7.96 V DC
$
I
Hi.
I have sensorsd running on a 4.0-current macppc.
It always worked fine and when min/max values of a sensor are
reached, a mail is sent to me.
Recently, a problem happened: each time I start the sensorsd daemon
(either on boot up or manually), I get the following warning mail:
28.00 degC
is that:
- it used to work
- it _only_ happens once on sensorsd startup, after that it works fine
as we can see 28c is not really even a valid temperature.
Indeed.
Thanks for the explanation.
--
Antoine
On Mon, Jul 17, 2006 at 11:42:01PM -0300, Gustavo Rios wrote:
Hey folks,
I am running a Dell Precision Workstation, is it possible to have
sensors working with such hardware? Any special consideration?
First, try 'sysctl hw.sensors'. If you get nothing (like on the Dell I
am using right
Hey folks,
I am running a Dell Precision Workstation, is it possible to have
sensors working with such hardware? Any special consideration?
Thanks in advance.
Hello. I have not used sensorsd on OpenBSD before, but am trying to
learn. I have read sensorsd(8) and sensorsd.conf(5) from OpenBSD 3.9
and the configuration looks very simple. However, i have a couple quick
questions:
The lines in sensorsd.conf start with hw.sensors.N (where N is a small
temperature, in your
/etc/sensorsd.conf file, you could put something like:
hw.sensors.0:high=60C:\
:command=echo %2 \(high=%4\) | mail -s [`hostname`] sensorsd WARNING \(CPU
Temp.\) root
Regards,
--
Antoine
hw.sensors.4
will tell you. Sensorsd is more for watching for threshholds and
boundary readings, rather than a real-time display of the current reading.
If you're programming, you can also use sysctl(3); it would be something
like sysctl({CTL_HW, HW_SENSORS, 4}, 3, some_allocated_buffer
Thank you to those who responded! I can figure out sensorsd.conf now.
Also thank you to the developers who created such a simple way to
monitor the sensors. I've configured sensors on other operating systems
that have been a much greater hassle.
On Mon, Jan 30, 2006 at 12:57:24PM +0800, John Wong wrote:
after upgrade to 3.9beta/i386, sensorsd can not start
when i start the sensorsd, it show the error message
shell$: /usr/sbin/sensorsd
sensorsd: sysctl: No such file or directory
Just fixed that in -current. Thanks for the report
On Monday 30 January 2006 05:57, John Wong wrote:
after upgrade to 3.9beta/i386, sensorsd can not start
when i start the sensorsd, it show the error message
shell$: /usr/sbin/sensorsd
sensorsd: sysctl: No such file or directory
I see the same behaviour on snapshot from Jan 24, i386.
--
viq
after upgrade to 3.9beta/i386, sensorsd can not start
when i start the sensorsd, it show the error message
shell$: /usr/sbin/sensorsd
sensorsd: sysctl: No such file or directory
what file or directory should i need?
shell$: cat /etc/sensorsd.conf
hw.sensors.0
Hi...
One quick stupid question. I'm looking for a way to get a mail when
sensorsd logs something to syslog. Is there an easy way to do this ?
For instance, today sensorsd reported the following :
Aug 27 15:27:21 mcp sensorsd[6314]: failure for hw.sensors.0:
46.40C/115.52F not within limits
Antoine Jacoutot wrote:
How can I make sensorsd or syslog to mail me this, without running a
parser every minute on /var/log/messages which looks overkill.
Answering to myself...
Allright, I had a check on sensorsd under current and it looks like in
3.8 I will be able to give a command
Antoine Jacoutot skrev:
How can I make sensorsd or syslog to mail me this, without running a
parser every minute on /var/log/messages which looks overkill.
man 5 sensorsd.conf
/kami
89 matches
Mail list logo
