Hello all,
Effective immediately, messages from list subscribers that are held by
list management software will be rejected.
Most frequent cause for this is a message that is too big. Default
limit is 50K, which is more than enough for a message, unless it gets
top-posted indefinitely without
Have you considered switched relays?http://www.hobby-boards.com/catalog/product_info.php?cPath=24&products_id=1504
http://www.aagelectronica.com/aag/index.htmlhttp://www.springbokshop.com/
http://www.arunet.co.uk/tkboyd/e1dhw.htmOn 11/4/06, Christian Magnusson <[EMAIL PROTECTED]> wrote:
In an attempt to optimise the 1wire
communications can you comment on the following:
Reading data
My current requirment is to read the volts every
two minutes (although would like it faster especially when I get my weather
station) from all channels of 2 x DS2450 (A/D), temperature from 4 x
Thanks Paul.
I’ll try the ./configure
--disable-owtcl technique next week.
Regarding owserver issue, this is all via
command line.
./owserver -d /dev/ttyS0
-p 3001 --error_level 4
26941
ttyS0 Ss+ 0:00 ./owserver -d /dev/ttyS0 -p
3001 --error_level 4
snmpmgr:/opt/owfs/
Looks like owtcl problem (and no libusb)If you aren't going to use owtcl, try./configure --disable-owtclI'm perplexed by the owserver in background problem. Is it being loaded from the command line, or within the nagios system. Perhaps Nagios doesn't allow owserver to fork into the background?
Paul
Upgrading to 2.5p5-4
might improve the stability… I don’t remember if 2.4p1 had any
major problems…
You should avoid start
owftpd and owhttpd if you don’t use them.
/opt/etc/init.d/S80owftpd
stop
/opt/etc/init.d/S80owhttpd
stop
Most important is to view
the errors from owser
