NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
couch_potatoe
Dec 12, 2012Aspirant
NAS 1100 / RAIDiator 4.1.10: ReadyDLNA 1.0.25 fails to start
Hi Folks, Recent problems with my 1100 and ReadyDLNA are driving me round the bend! Up until a few months ago everything was fine, now I've got to the point that I can't even start the DLNA ser...
richtoy
Dec 24, 2012Tutor
Hi Andy,
I have similar issues on my X6 box. Do you have more than one DLNA client? I do and this appears to make the problems much worse and this has led me to believe that it is an issue with how the program is built. The source is available on sourceforge and only uses the -pthreads flag in the makefile but you can find many examples of makefiles for Solaris (Sparc) where the -D_REENTRANT preprocessor flag is also present. The -D_REENTRANT flag causes the compiler to include a thread safe errno and -ptheads should be sufficient with the latest versions of gcc. A non thread safe errno can give these type of errors where a system call from one thread sets errno only for its value to be (incorrectly) interpreted by another thread giving leading to hard to understand errors. Without knowing the environment used to build the daemon its impossible to know if this the case. I will root my machine and try your fix to see if it makes any difference.
Richard
I have similar issues on my X6 box. Do you have more than one DLNA client? I do and this appears to make the problems much worse and this has led me to believe that it is an issue with how the program is built. The source is available on sourceforge and only uses the -pthreads flag in the makefile but you can find many examples of makefiles for Solaris (Sparc) where the -D_REENTRANT preprocessor flag is also present. The -D_REENTRANT flag causes the compiler to include a thread safe errno and -ptheads should be sufficient with the latest versions of gcc. A non thread safe errno can give these type of errors where a system call from one thread sets errno only for its value to be (incorrectly) interpreted by another thread giving leading to hard to understand errors. Without knowing the environment used to build the daemon its impossible to know if this the case. I will root my machine and try your fix to see if it makes any difference.
Richard
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!