[Owfs-developers] zeroconf requirements?

[Christian Magnusson]

 

 

What are the requirements for building with zero-conf
support?

 

I have NOT found the “libdns_sd” which
the configure script seem to look for…. The only thing I find is “libhowl”
for my Fedora installation… and it does not contain the same functions.

Libhowl is also possible to use for OpenWRT and NSLU2…


 

Could anyone help me with this…

 

/Christian

 






-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] zeroconf requirements?

[Paul Alfille]

Hi Christian,There is some documentation at http://www.owfs.org/index.php?page=bonjour_libraryBasically we use the Apple libraries: 
http://developer.apple.com/networking/bonjour/It compiles under linux and GPL easily, but doesn't use autoconf. If I remember, you need to go to their "Posix directory"  and something like "make os=linux" (it's in the readme).
PaulOn 10/9/06, Christian Magnusson <[EMAIL PROTECTED]> wrote:













 

 

What are the requirements for building with zero-conf
support?

 

I have NOT found the "libdns_sd" which
the configure script seem to look for…. The only thing I find is "libhowl"
for my Fedora installation… and it does not contain the same functions.

Libhowl is also possible to use for OpenWRT and NSLU2…


 

Could anyone help me with this…

 

/Christian

 







-Take Surveys. Earn Cash. Influence the Future of ITJoin SourceForge.net's Techsay panel and you'll get the chance to share youropinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___Owfs-developers mailing listOwfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Building on OS/X

[Paul Alfille]

So you want to keep the nested function and force nested with a command line switch? Sounds good to me. I found extensive discussions about executable stacks, trampolines, etc.Otherwise the CVS has a work-around for Mac in ow_dir.c using a mutex and global variable.
Paul AlfilleOn 10/9/06, Peter Kropf <[EMAIL PROTECTED]> wrote:
Things are progressing. I've just committed a couple of changes thatwill allow for testing the compiler for nested function support duringthe initial bootstrap / configure steps. See acinclude.m4 and
configure.ac for the changes. And the ow_dir.c module has been updatedto use the new NO_NESTED_FUNCTIONS macro to determine which way to go.I thought this might be a better way to support nested functionsinstead of making it platform specific.
With the new code in place, the ow_dir.c module compiles. But thebuild craps out on the ow_fake.c module. There's another nestedfunction there. I haven't fixed it yet but should get to it tomorrow.
I would appreciate another pair of eyes looking over the changes I'vemade to make sure they're sane and that I haven't snafued any otherplatforms.Thanks.- PeterOn 10/8/06, Paul Alfille <
[EMAIL PROTECTED]> wrote:> Ok, I think the fix is in, though I can't test it without the correct target> platform.>> Basically, I made global variables for the information we were tacitly
> passing, and put in a lock to protect them. Should be a big performance> problem -- these directories are being pulled from RAM, not the 1-wire bus.> Made the changes __MacOSX__ specific.>
>> On 10/8/06, Paul Alfille <[EMAIL PROTECTED]> wrote:> > I can see why you hesitated with the nested function. There is no place to> pass data into the function. Our choices are:
> > 1. Write our own "twalk"> > 2. Use global variables and a mutex.> >> > I guess I'll do the later for the Mac. What's the "#define" for Mac?> >> > Paul
> >> >> >> > On 10/8/06, Peter Kropf < [EMAIL PROTECTED]> wrote:> > > Ok, I've fixed the makefile problem - there was an extra space after a
> > > backslash.> > >> > > The nested function seems to be a bit over my head right now. I'm not> > > seeing a reasonable way to pass the pn2 variable to the action> > > function. But I will take another shot at it tomorrow evening unless
> > > someone else gets there first ;-)> > >> > > - Peter> > >> > >> > > On 10/7/06, Peter Kropf < [EMAIL PROTECTED]
> wrote:> > > > I'll start looking into it tonight but I'm not going to be able to> > > > spend too much time on it. Getting late here and I need to be up & out> > > > early tomorrow morning. Worst case, I'll start on it again tomorrow
> > > > evening.> > > >> > > > - Peter> > > >> > > >> > > > On 10/7/06, Paul Alfille <
[EMAIL PROTECTED] > wrote:> > > > > Hi Peter,> > > > >> > > > > In the first instance, the tab was probably added automatically by> the> > > > > editor. Tabs are handled specially in makefiles, and if you can fix
> it, I'd> > > > > be pleased.> > > > >> > > > > Nested functions: They are there only for convenience. All the ones> dealing> > > > > with threads were removed because of changes in recent linux kernels
> -- a> > > > > security risk. Removing them involves some work with packing the> relevant> > > > > shared variables in a structure, and allocating memory if the> subroutine is
> > > > > in a separate thread (so heap variables in one thread don't get> reclaimed> > > > > before the other thread is done with them).> > > > >> > > > > Again, if you want to tackle this, I'd be pleased. Otherwise I'll
> look at it> > > > > tomorrow.> > > > >> > > > > A new release for the Mac platform would be great. The owshell> functions> > > > > would be especially useful there since FUSE is not supported as far
> as I> > > > > know making shell access to the 1-wire bus is difficult.> > > > >> > > > > Paul Alfille> > > > >> > > > >
> > > > > On 10/8/06, Peter Kropf <[EMAIL PROTECTED]> wrote:> > > > > >> > > > > > Hi -> > > > > >
> > > > > > Due to the recent demise of my Thinkpad, I'm not working on a> MacBook> > > > > > Pro. Things here are different but still very similar. But pretty> fun.
> > > > > >> > > > > > I'm just getting around to building owfs for the first time on> MacOSX> > > > > > and have run into a couple of problems. I would like to know if
> anyone> > > > > > else is using MacOSX for their development. There's at least one> > > > > > outstanding fix needed for the Python module and I'd like to get> > > > > > moving on getting it done.
> > > > > >> > > > > > The first problem is pretty minor but I'm not sure why it's> happening.> > > > > > The generated src/man/Makefile, there's a problem:
> > > > > >> > > > > > fog:~/src/owfs peter$ make> > > > > > Making all in src> > > > > > Making all in include> > > > > > make  all-am
> > > > > > Making all in man> > > > > > Makefile:531: *** missing separator (did you mean TAB instead of 8> > > > > > spaces?).  Stop.> > > > > > make[1]: *** [all-recursive] Error 1
> > > > > > make: *** [all-recursive] Error 1> > > > > > 

Re: [Owfs-developers] PHP Mem leak

[Paul Alfille]

I'd rather fix than make an awkward workaround.Now which process used all the memory? owserver or php(owphp)? They both have a cache and essentially the same caching code, etc. If owserver isn't bloating up, then there is probably a memory leak in owphp. Should be easy to find, it's only about 100 lines of code.
Paul AlfilleP.S. As a side note, the cache is jettisoned every hour or so, so it's unlikely to expand uncontrollably.On 10/9/06, Roberto Spadim
 <[EMAIL PROTECTED]> wrote:hello guys, i was using php with 8 ds1820 and ds2480 and another ds that
is an input/output digital (i don't remenber number family=05)i was running php ow lib for one week without stop, i was removing andput devices, after one week i get htop to view some informationsphp was 204M of mem use, i think that the cache, cause i was using
devices that wasn't on bus and after i put it again on bus, i'm usingowserver in init("172.16.0.1:1234");can i set cache off? maybe an getenv('OW_CACHE_OFF')==1 ???
i'm using cache on owserver, php is just an lib to acces owserverwithout using fuse and without putting ds2480 on my serialthankx guys,with this i think that problem will end, php haveputenv("OW_CACHE_OFF=1") :)
bye-Take Surveys. Earn Cash. Influence the Future of ITJoin SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cashhttp://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___Owfs-developers mailing listOwfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Building on OS/X

[Peter Kropf]

I modified ow_dir.c to use the NO_NESTED_FUNCTIONS macro instead of
the __MacOS__ macro. The change has been check into CVS.

- Peter


On 10/9/06, Paul Alfille <[EMAIL PROTECTED]> wrote:
> So you want to keep the nested function and force nested with a command line
> switch? Sounds good to me. I found extensive discussions about executable
> stacks, trampolines, etc.
>
> Otherwise the CVS has a work-around for Mac in ow_dir.c using a mutex and
> global variable.
>
> Paul Alfille
>
>
> On 10/9/06, Peter Kropf <[EMAIL PROTECTED]> wrote:
> >
> > Things are progressing. I've just committed a couple of changes that
> > will allow for testing the compiler for nested function support during
> > the initial bootstrap / configure steps. See acinclude.m4 and
> > configure.ac for the changes. And the ow_dir.c module has been updated
> > to use the new NO_NESTED_FUNCTIONS macro to determine which way to go.
> > I thought this might be a better way to support nested functions
> > instead of making it platform specific.
> >
> > With the new code in place, the ow_dir.c module compiles. But the
> > build craps out on the ow_fake.c module. There's another nested
> > function there. I haven't fixed it yet but should get to it tomorrow.
> >
> > I would appreciate another pair of eyes looking over the changes I've
> > made to make sure they're sane and that I haven't snafued any other
> > platforms.
> >
> > Thanks.
> >
> > - Peter
> >
> >
> > On 10/8/06, Paul Alfille < [EMAIL PROTECTED]> wrote:
> > > Ok, I think the fix is in, though I can't test it without the correct
> target
> > > platform.
> > >
> > > Basically, I made global variables for the information we were tacitly
> > > passing, and put in a lock to protect them. Should be a big performance
> > > problem -- these directories are being pulled from RAM, not the 1-wire
> bus.
> > > Made the changes __MacOSX__ specific.
> > >
> > >
> > > On 10/8/06, Paul Alfille <[EMAIL PROTECTED]> wrote:
> > > > I can see why you hesitated with the nested function. There is no
> place to
> > > pass data into the function. Our choices are:
> > > > 1. Write our own "twalk"
> > > > 2. Use global variables and a mutex.
> > > >
> > > > I guess I'll do the later for the Mac. What's the "#define" for Mac?
> > > >
> > > > Paul
> > > >
> > > >
> > > >
> > > > On 10/8/06, Peter Kropf < [EMAIL PROTECTED]> wrote:
> > > > > Ok, I've fixed the makefile problem - there was an extra space after
> a
> > > > > backslash.
> > > > >
> > > > > The nested function seems to be a bit over my head right now. I'm
> not
> > > > > seeing a reasonable way to pass the pn2 variable to the action
> > > > > function. But I will take another shot at it tomorrow evening unless
> > > > > someone else gets there first ;-)
> > > > >
> > > > > - Peter
> > > > >
> > > > >
> > > > > On 10/7/06, Peter Kropf < [EMAIL PROTECTED] > wrote:
> > > > > > I'll start looking into it tonight but I'm not going to be able to
> > > > > > spend too much time on it. Getting late here and I need to be up &
> out
> > > > > > early tomorrow morning. Worst case, I'll start on it again
> tomorrow
> > > > > > evening.
> > > > > >
> > > > > > - Peter
> > > > > >
> > > > > >
> > > > > > On 10/7/06, Paul Alfille < [EMAIL PROTECTED] > wrote:
> > > > > > > Hi Peter,
> > > > > > >
> > > > > > > In the first instance, the tab was probably added automatically
> by
> > > the
> > > > > > > editor. Tabs are handled specially in makefiles, and if you can
> fix
> > > it, I'd
> > > > > > > be pleased.
> > > > > > >
> > > > > > > Nested functions: They are there only for convenience. All the
> ones
> > > dealing
> > > > > > > with threads were removed because of changes in recent linux
> kernels
> > > -- a
> > > > > > > security risk. Removing them involves some work with packing the
> > > relevant
> > > > > > > shared variables in a structure, and allocating memory if the
> > > subroutine is
> > > > > > > in a separate thread (so heap variables in one thread don't get
> > > reclaimed
> > > > > > > before the other thread is done with them).
> > > > > > >
> > > > > > > Again, if you want to tackle this, I'd be pleased. Otherwise
> I'll
> > > look at it
> > > > > > > tomorrow.
> > > > > > >
> > > > > > > A new release for the Mac platform would be great. The owshell
> > > functions
> > > > > > > would be especially useful there since FUSE is not supported as
> far
> > > as I
> > > > > > > know making shell access to the 1-wire bus is difficult.
> > > > > > >
> > > > > > > Paul Alfille
> > > > > > >
> > > > > > >
> > > > > > > On 10/8/06, Peter Kropf <[EMAIL PROTECTED]> wrote:
> > > > > > > >
> > > > > > > > Hi -
> > > > > > > >
> > > > > > > > Due to the recent demise of my Thinkpad, I'm not working on a
> > > MacBook
> > > > > > > > Pro. Things here are different but still very similar. But
> pretty
> > > fun.
> > > > > > > >
> > > > > > > > I'm just getting around to building owfs for the first time on
> > > MacOSX
> > > > > > > > and have run into a couple o

Re: [Owfs-developers] PHP Mem leak

[Roberto Spadim]

ow php :)
owserver work very fine

Paul Alfille escreveu:
> I'd rather fix than make an awkward workaround.
>
> Now which process used all the memory? owserver or php(owphp)? They 
> both have a cache and essentially the same caching code, etc. If 
> owserver isn't bloating up, then there is probably a memory leak in 
> owphp. Should be easy to find, it's only about 100 lines of code.
>
> Paul Alfille
>
> P.S. As a side note, the cache is jettisoned every hour or so, so it's 
> unlikely to expand uncontrollably.
>
> On 10/9/06, *Roberto Spadim * <[EMAIL PROTECTED] 
> > wrote:
>
> hello guys, i was using php with 8 ds1820 and ds2480 and another
> ds that
> is an input/output digital (i don't remenber number family=05)
> i was running php ow lib for one week without stop, i was removing and
> put devices, after one week i get htop to view some informations
> php was 204M of mem use, i think that the cache, cause i was using
> devices that wasn't on bus and after i put it again on bus, i'm using
> owserver in init("172.16.0.1:1234 ");
> can i set cache off? maybe an getenv('OW_CACHE_OFF')==1 ???
> i'm using cache on owserver, php is just an lib to acces owserver
> without using fuse and without putting ds2480 on my serial
>
> thankx guys,
> with this i think that problem will end, php have
> putenv("OW_CACHE_OFF=1") :)
> bye
>
> -
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to
> share your
> opinions on IT & business topics through brief surveys -- and earn
> cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> 
> 
> ___
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> 
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
>
> 
> Esta mensagem foi verificada pelo E-mail Protegido Terra 
> .
> Scan engine: McAfee VirusScan / Atualizado em 06/10/2006 / Versão: 
> 4.4.00/4868
> Proteja o seu e-mail Terra: http://mail.terra.com.br/
> 
>
> -
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> 
>
> ___
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>   


-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
___
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Re: [Owfs-developers] Building on OS/X

[Peter Kropf]

Just an FYI - I've modified more of the code base to segregate nested
functions for those platforms that don't support them. I don't think
this work is finished yet and I'll continue working on it over the
next few days. If anyone finds any problems on other platforms
(non-MacOSX) let me know and I'll help getting things resolved.

- Peter



On 10/9/06, Peter Kropf <[EMAIL PROTECTED]> wrote:
> I modified ow_dir.c to use the NO_NESTED_FUNCTIONS macro instead of
> the __MacOS__ macro. The change has been check into CVS.
>
> - Peter
>
>
> On 10/9/06, Paul Alfille <[EMAIL PROTECTED]> wrote:
> > So you want to keep the nested function and force nested with a command line
> > switch? Sounds good to me. I found extensive discussions about executable
> > stacks, trampolines, etc.
> >
> > Otherwise the CVS has a work-around for Mac in ow_dir.c using a mutex and
> > global variable.
> >
> > Paul Alfille
> >
> >
> > On 10/9/06, Peter Kropf <[EMAIL PROTECTED]> wrote:
> > >
> > > Things are progressing. I've just committed a couple of changes that
> > > will allow for testing the compiler for nested function support during
> > > the initial bootstrap / configure steps. See acinclude.m4 and
> > > configure.ac for the changes. And the ow_dir.c module has been updated
> > > to use the new NO_NESTED_FUNCTIONS macro to determine which way to go.
> > > I thought this might be a better way to support nested functions
> > > instead of making it platform specific.
> > >
> > > With the new code in place, the ow_dir.c module compiles. But the
> > > build craps out on the ow_fake.c module. There's another nested
> > > function there. I haven't fixed it yet but should get to it tomorrow.
> > >
> > > I would appreciate another pair of eyes looking over the changes I've
> > > made to make sure they're sane and that I haven't snafued any other
> > > platforms.
> > >
> > > Thanks.
> > >
> > > - Peter
> > >
> > >
> > > On 10/8/06, Paul Alfille < [EMAIL PROTECTED]> wrote:
> > > > Ok, I think the fix is in, though I can't test it without the correct
> > target
> > > > platform.
> > > >
> > > > Basically, I made global variables for the information we were tacitly
> > > > passing, and put in a lock to protect them. Should be a big performance
> > > > problem -- these directories are being pulled from RAM, not the 1-wire
> > bus.
> > > > Made the changes __MacOSX__ specific.
> > > >
> > > >
> > > > On 10/8/06, Paul Alfille <[EMAIL PROTECTED]> wrote:
> > > > > I can see why you hesitated with the nested function. There is no
> > place to
> > > > pass data into the function. Our choices are:
> > > > > 1. Write our own "twalk"
> > > > > 2. Use global variables and a mutex.
> > > > >
> > > > > I guess I'll do the later for the Mac. What's the "#define" for Mac?
> > > > >
> > > > > Paul
> > > > >
> > > > >
> > > > >
> > > > > On 10/8/06, Peter Kropf < [EMAIL PROTECTED]> wrote:
> > > > > > Ok, I've fixed the makefile problem - there was an extra space after
> > a
> > > > > > backslash.
> > > > > >
> > > > > > The nested function seems to be a bit over my head right now. I'm
> > not
> > > > > > seeing a reasonable way to pass the pn2 variable to the action
> > > > > > function. But I will take another shot at it tomorrow evening unless
> > > > > > someone else gets there first ;-)
> > > > > >
> > > > > > - Peter
> > > > > >
> > > > > >
> > > > > > On 10/7/06, Peter Kropf < [EMAIL PROTECTED] > wrote:
> > > > > > > I'll start looking into it tonight but I'm not going to be able to
> > > > > > > spend too much time on it. Getting late here and I need to be up &
> > out
> > > > > > > early tomorrow morning. Worst case, I'll start on it again
> > tomorrow
> > > > > > > evening.
> > > > > > >
> > > > > > > - Peter
> > > > > > >
> > > > > > >
> > > > > > > On 10/7/06, Paul Alfille < [EMAIL PROTECTED] > wrote:
> > > > > > > > Hi Peter,
> > > > > > > >
> > > > > > > > In the first instance, the tab was probably added automatically
> > by
> > > > the
> > > > > > > > editor. Tabs are handled specially in makefiles, and if you can
> > fix
> > > > it, I'd
> > > > > > > > be pleased.
> > > > > > > >
> > > > > > > > Nested functions: They are there only for convenience. All the
> > ones
> > > > dealing
> > > > > > > > with threads were removed because of changes in recent linux
> > kernels
> > > > -- a
> > > > > > > > security risk. Removing them involves some work with packing the
> > > > relevant
> > > > > > > > shared variables in a structure, and allocating memory if the
> > > > subroutine is
> > > > > > > > in a separate thread (so heap variables in one thread don't get
> > > > reclaimed
> > > > > > > > before the other thread is done with them).
> > > > > > > >
> > > > > > > > Again, if you want to tackle this, I'd be pleased. Otherwise
> > I'll
> > > > look at it
> > > > > > > > tomorrow.
> > > > > > > >
> > > > > > > > A new release for the Mac platform would be great. The owshell
> > > > functions
> > > > > > > > would be especially useful there since