Hello.
The problem was in an old apache2. :-(
My CGI scripts is working very good now, after apache2 update!
Thank you very much
--
== Henry Pootel ==
--
Check out the vibrant tech community on one of the world's
Hello again.
I've found a strange situation. I'll try to resolve it.
While, what you say about this.
Do you remember "my lost first byte" of owwrite?
I use CGI perl module and have a simple script:
cat index.pl
#!/usr/bin/perl
use CGI;
use OWNet;
my $q = CGI->new;
print $q->header( -Content-typ
On 16.10.2016 13:41, Jan Kandziora wrote:
> Am 16.10.2016 um 11:27 schrieb Henry Pootel:
>> ;-) But we are can't send binary file by cli.
>>
> Then we have to change that. I change owwrite so it reads stdin instead
> of complaining about a missing value argument.
+1
--
-- Matthias Urlichs
-
Am 16.10.2016 um 11:27 schrieb Henry Pootel:
>
> ;-) But we are can't send binary file by cli.
>
Then we have to change that. I change owwrite so it reads stdin instead
of complaining about a missing value argument.
Kind regards
Jan
---
Dear friends!
I'm sorry, I distract you from your work...
I've made a mistake, I'll find it by own.
So, I've wrote a simple script and test my situation.
root@CONSTANT:~> cat test.pl
#!/usr/bin/perl
use OWNet;
use IO::Compress::Gzip qw(gzip $GzipError) ;
use IO::Uncompress::Gunzip qw(gunzip $Gun
On 16.10.2016 01:18, Stefano Miccoli wrote:
> First, owwrite seems to have problems with nul characters in his arguments
*All* programs have problems with NUL characters in their arguments.
You don't need confirmation for that, that's basic C/UNIX.
To fix that, you need a flag for owwrite that rea
> On 15 Oct 2016, at 15:23, Henry Pootel wrote:
>
> root@CONSTANT:~> owwrite -s 172.19.19.10 /relay_setting/RELAY_SET `cat ee`
I see a couple of problems here.
First, owwrite seems to have problems with nul characters in his arguments, but
please wait for confirmation by Jan.
Second, assum
Am 15.10.2016 um 19:35 schrieb Henry Pootel:
>
> Of course, I can try owwrite an ascii data without compression.
> But, it's a workaround of the binary write. It's not a decision.
>
We had those 0x00 problems at various occasions. Let me look into it,
maybe it's easily fixable.
Kind regards
Thank you, Matthias, for your opinion. I see you, but...
15.10.2016 17:43, Matthias Urlichs wrote:
> On 15.10.2016 15:23, Henry Pootel wrote:
>> Some bytes are lost. (00 - this bytes are lost!!! May be something
>> else..)
> Null bytes are end-of-string indicators in C. Apparently something
> igno
Am 15.10.2016 um 17:43 schrieb Matthias Urlichs:
> On 15.10.2016 15:23, Henry Pootel wrote:
>> Some bytes are lost. (00 - this bytes are lost!!! May be something
>> else..)
> Null bytes are end-of-string indicators in C. Apparently something
> ignores the binary data length.
>
> May I ask what you
On 15.10.2016 15:23, Henry Pootel wrote:
> Some bytes are lost. (00 - this bytes are lost!!! May be something
> else..)
Null bytes are end-of-string indicators in C. Apparently something
ignores the binary data length.
May I ask what your use case for sending binary data to your 1wire
server via O
Hello dear friends.
New tests!
root@CONSTANT:~> echo -n
'1,NO,0,OFF,0,0,,#2,NO,0,OFF,0,0,,#3,NO,0,OFF,0,0,,#4,NO,0,OFF,0,0,,#5,NO,0,OFF,0,0,,#6,NO,0,OFF,0,0,,#7,NO,0,OFF,0,0,,#8,NO,0,OFF,0,0,,#'|
gzip -c > ee
root@CONSTANT:~> cat ee | hexdump -C
1f 8b 08 00 03 2a 02 58 00 03 33 d
Hello.
Using owfs-3.1p4.
I need to write binary data to an external sensor.
I do this settings:
owfs.conf
...
SCRIPT: "RELAY_SET", "constant_family", b1024, 1, u, /opt/_read,
/opt/_write, ''
...
The main is b1024. Is it right?
And write from a client by perl script:
OWNet::write( "$dev_ip:4
13 matches
Mail list logo
