|
osdir.com mailing list archive |
|
Subject: Re: strange syslog messages - msg#00253List: handhelds.opie> Hi, > > I am getting a lot of the following messages (which I am not sure are opie > related ? I guesses because of the "Q" .. ?) > > Oct 18 19:38:49 familiar user.notice root: QServerSocket: failed to bind or > listen to the socket Oct 18 19:38:49 familiar user.notice root: Failed to > bind to port 4243 Oct 18 19:38:49 familiar user.notice root: QServerSocket: > failed to bind or listen to the socket Oct 18 19:38:49 familiar user.notice > root: Failed to bind to port 4242 O > > What is it ? Opie is binding to the ports 4242(ftp) and 4243(qcopbridge) this is needed for syncing.. Opie got terminated and restarted somehow and did not properly release the sockets.. I guess this is a kernel security feature. regards Holger > > Marc Baaden -- _____________________________________________ Holger 'zecke' Freyther developer Project OPIE- the Open Palmtop Integrated Environment http://opie.handhelds.org | http://www.opie.info (german) IRC: irc.freenode.net #opie #opie.de _______________________________________________ Open Source User Interface and Apps built on Qt Embedded Opie mailing list Opie@xxxxxxxxxxxxx http://handhelds.org/mailman/listinfo/opie
Thread at a glance:
Previous Message by Date: (click to view message preview)opie qt-embedded threadingHi all, is Opie compiled agains the qt-embedded threaded version or agains the regular version. If it is the regular, what would the effect be if it is run agains the threaded version. More generally, what do I need to do to have an application that wants to use qt from a threaded environment Thanx W _______________________________________________ Open Source User Interface and Apps built on Qt Embedded Opie mailing list Opie@xxxxxxxxxxxxx http://handhelds.org/mailman/listinfo/opie Next Message by Date: click to view message previewIpaq freezes, 2nd roundHello everybody, as I was advised on this list last week, by now I have reinstalled my Ipaq, this time with bootldr 2.18.01 to get around the device freezes encountered on resume. I've started out with the bootopie image of familiar v0.6-rc1. This seemed to be stable. Over a period of 2 hours I switched the Ipaq on and off several times with pauses of different length (1 to 25 minutes) in between. No glitches there. After that I started updating OPIE to opie-unstable. I started with the following packages: opie-opiealarm, qt-embedded, qt-embedded-rotation,libopie, opie-base, opie-taskbar After this I rebooted the device and installed opie-qcop. After this package I restarted OPIE (no reboot). Since I figured that the basic system had now been updated, I wanted to do some more checking. I switched the Ipaq off and 1 minute later tried to switch it on again. However, this failed, the Ipaq froze. So the bootloader doesn't seem to be my problem. It seems to be somewhere in the basic OPIE system. Upgrading the basic system to opie-unstable of October 15th didn't change that behavior. This is kinda frustrating to me since my Ipaq is somewhat unusable with alarms that go off but send the gadget right into digital nirvana and as a computer that generally has to be rebooted in the worst of all moments (my respects, Mr. Murphey). So, please tell me: 1. Dou you gurus out there consider it likely that qcop is responsible for the glitches? 2. If OPIE has its own power management, what exactly happens on resume? (I'm not a coder, at least not C, so I won't understand the process just from looking at the code) What steps are taken by the OPIE environment? BTW, I know about the /etc/resume-scripts end of the process; that's not what I'm talking about here, though. 3. Does somebody out there have a Ipaq H3760 with a working familiar/OPIE combination? What versions? Thanx in advance Alex smime.p7s Description: S/MIME Cryptographic Signature Previous Message by Thread: click to view message previewRe: strange syslog messagesMy guess is this has to do with the FTP server OPIE is running (for Qtopia Desktop). Maybe the port is already open? On Fri, 2002-10-18 at 20:31, Marc Baaden wrote: > > Hi, > > I am getting a lot of the following messages (which I am not sure are opie > related ? I guesses because of the "Q" .. ?) > > Oct 18 19:38:49 familiar user.notice root: QServerSocket: failed to bind or > listen to the socket > Oct 18 19:38:49 familiar user.notice root: Failed to bind to port 4243 > Oct 18 19:38:49 familiar user.notice root: QServerSocket: failed to bind or > listen to the socket > Oct 18 19:38:49 familiar user.notice root: Failed to bind to port 4242 > O > > What is it ? > > Marc Baaden > > -- > Dr. Marc Baaden - Laboratory of Molecular Biophysics, Oxford University > mailto:baaden@xxxxxxxxxxx - ICQ# 11466242 - http://www.marc-baaden.de > FAX/Voice +49 697912 39550 - Tel: +44 1865 275380 or +33 609 843217 > > > _______________________________________________ > Open Source User Interface and Apps built on Qt Embedded > Opie mailing list > Opie@xxxxxxxxxxxxx > http://handhelds.org/mailman/listinfo/opie _______________________________________________ Open Source User Interface and Apps built on Qt Embedded Opie mailing list Opie@xxxxxxxxxxxxx http://handhelds.org/mailman/listinfo/opie Next Message by Thread: click to view message previewthreads on Qtopia or OPIE?Is the libc for the Zaurus (or Familiar or OpenZaurus) built with thread support? Can I get away with calling things that malloc etc as long as I avoid calling Qt events? I'm kind of confused that there is a libpthread but no qte-mt. -- Ben Jackson <ben@xxxxxxx> http://www.ben.com/ _______________________________________________ Open Source User Interface and Apps built on Qt Embedded Opie mailing list Opie@xxxxxxxxxxxxx http://handhelds.org/mailman/listinfo/opie
Web Hosting Reviews from OSDir.com Sister Site iBizWebHosting.com
|
|