[FreeNX-kNX] Re: FreeNX gets Client Infrastructure
Sunil
funtoos at yahoo.com
Sun Mar 13 06:14:42 UTC 2005
ok, I changed the Logger.h a bit and generated all
logs.
only ERROR entry was:
ERROR: NXTransport (nxssh): set default parameter
'NX_SshName'.
is that harmful? it doesn't look like it because it
just uses "nxssh" by default for that parameter, which
is probably fine.
Then, something else caught my eye:
INFO: Connecting to 'linuxhost'.
DEBUG: NXProcess: wait for select.
DEBUG: NXProcess: there is data to read.
DEBUG:
---
READ: DEBUG: nxssh
DEBUG: -nx
DEBUG: -v
DEBUG: -i
DEBUG: /usr/NX/share/client.id_dsa.key
DEBUG: nx at linuxhost
DEBUG: -B
DEBUG: - end process args
---
DEBUG: NXProtocol: line does not contain token NX.
DEBUG: NXProtocol: line is: DEBUG: nxssh
DEBUG: NXProtocol: line does not contain token NX.
DEBUG: NXProtocol: line is: DEBUG: -nx
DEBUG: NXProtocol: line does not contain token NX.
DEBUG: NXProtocol: line is: DEBUG: -v
DEBUG: NXProtocol: line does not contain token NX.
DEBUG: NXProtocol: line is: DEBUG: -i
DEBUG: NXProtocol: line does not contain token NX.
DEBUG: NXProtocol: line is: DEBUG:
/usr/NX/share/client.id_dsa.key
DEBUG: NXProtocol: line does not contain token NX.
DEBUG: NXProtocol: line is: DEBUG: nx at linuxhost
DEBUG: NXProtocol: line does not contain token NX.
DEBUG: NXProtocol: line is: DEBUG: -B
DEBUG: NXProtocol: line does not contain token NX.
DEBUG: NXProtocol: line is: DEBUG: - end process args
DEBUG: NXProcess: wait for select.
DEBUG: NXProcess: there is data to read.
DEBUG: NXProcess: wait for select.
and last three messages are repeated endlessly.
nxrun sees all the aguments printed by the child after
the fork but before the exec of the nxssh process.
After that it says data available to read but doesn't
read anything. As far as I can see it is supposed to
read the same data as is being put into sshlog(stdout
of nxssh). Is there a dup() issue?
--- Lawrence Roufail <lroufail at nc.rr.com> wrote:
> It just logs to stdout/stderr. You could use the
> fdie flags. That
> would send output to nxcompsh.log
>
> - L
>
> On Sat, 2005-03-12 at 20:36, Sunil wrote:
> > I am running:
> >
> > nxrun ~/.nx/config/MySession.conf -i -l die
> >
> > I don't see any log output to my screen. The
> source is
> > compiled with -DNX_ENABLE_LOGGING. That's one of
> the
> > bizzare things I couldn't explain. What underlying
> > print function does the logger use?
> >
> > I passed in the '-v' to nxssh as you suggested and
> > sshlog looks fine, no errors.
> >
> > anymore ideas?
> >
> > --- LROUFAIL at nc.rr.com wrote:
> >
> > > I would try two things.
> > >
> > > first, run nxrun with the logging on:
> > >
> > > ./nxrun -l ide
> > >
> > > This will tell me where the process is getting
> hung.
> > >
> > > If ou want to change the code, you can add the
> -v
> > > option to nxssh. This will give you debugging
> from
> > > the ssh process. Look at
> > > TransportSSH::initConnection()
> > >
> > > - L
> > >
> > > ----- Original Message -----
> > > From: Sunil <funtoos at yahoo.com>
> > > Date: Saturday, March 12, 2005 3:04 pm
> > > Subject: [FreeNX-kNX] Re: FreeNX gets Client
> > > Infrastructure
> > >
> > > > I took a cvs snapshot(march 10) of freenx and
> > > built
> > > > nxrun.
> > > >
> > > > It runs pretty well on linux. Then I built it
> on
> > > > solaris. Apart from setenv being not there,
> the
> > > build
> > > > went fine. But when I run it, it hangs while
> > > > connecting to the nxserver on linux machine:
> > > >
> > > > I> /home/sunil/.nx/config/MySession.conf.
> > > > I> moznx - version .3 (based on NXRUN -
> version
> > > > 1.3.1-1).
> > > > I> Connecting to 'linuxhost'.
> > > >
> > > > At this time nxssh is sleeping and nxrun is
> using
> > > > 100%cpu doing just repeated waitpid on nxssh.
> I
> > > > ultimately kill nxrun.
> > > >
> > > > sshlog contains:
> > > >
> > > > NX> 203 NXSSH running with pid: 24983^M
> > > > NX> 200 Connected to address: linuxhost on
> port:
> > > 22^M
> > > > NX> 202 Authenticating user: nx^M
> > > > NX> 208 Using auth method: publickey
> > > > HELLO NXSERVER - Version 1.4.0-02 OS_(GPL)
> > > > NX> 105 Killed by signal 2.
> > > >
> > > > nxserver.log shows only:
> > > >
> > > > -- NX SERVER START:
> > > > HELLO NXSERVER - Version 1.4.0-02 OS_(GPL)
> > > > NX> 105
> > > >
> > > > Anyone here knows what potential difference
> > > between
> > > > linux and solaris nx install can trigger this
> > > hang?
> > > >
> > > > Thanks,
> > > > -Sunil
> > > > --- Fabian Franz <FabianFranz at gmx.de> wrote:
> > > > > -----BEGIN PGP SIGNED MESSAGE-----
> > > > > Hash: SHA1
> > > > >
> > > > > The Internet, 11th of March 2005,
> > > > >
> > > > > The FreeNX project is glad to announce that
> two
> > > > > independent client
> > > > > projects have joined the FreeNX efforts.
> > > > >
> > > > > 1) nxc project lead by Lawrence Roufail.
> > > > > 2) gnx project lead by Gustavo Noronha
> Silva.
> > > > >
> > > > > Both projects provide their source code
> under
> > > the
> > > > > GPL license.
> > > > >
> > > > > About the nxc project
> > > > > - ---------------------------------
> > > > >
> > > > > nxc is an OS-independent nx(client/connect)
> > > library.
> > > > > It allows writing
> > > > > a very simple NX client with just about 10
> lines
> > > of
> > > > > C++ code.
> > > > >
> > > > > nxc also includes two sample client
> > > implementations:
> > > > >
> > > > > 1) moznx -- a browser plugin for mozilla
> based
> > > > > browsers
> > > > > 2) nxrun -- a very simple, but complete
> > > command
> > > > > line client
> > > > >
> > > > > Note that the nxcompsh, nxdriver and nxrun
> parts
> > > of
> > > > > nxc are based on
> > > > > initial work done by NoMachine which was
> > > released
> > > > > under the GPL. This
> > > > > initial code was polished up by Lawrence and
> > > brought
> > > > > up to date. It
> > > > > now works with both, commercial 1.4.0
> versions
> > > as
> > > > > well as FreeNX
> > > > > 1.4.0-02 (aka FreeNX 0.2.4 - 0.3.0).
> > > > >
> > > > > nxc does currently build and work on Linux
> and
> > > > > Windows systems.
> > > > >
> > > > > You can find more detailed information about
> > > moznx
> > > > > on Lawrence's home
> > > > > page:
> > > > >
> > > > > http://home.nc.rr.com/moznx/
> > > > >
> > > > > The newest nxc source code has now been
> checked
> > > into
> > > > > the FreeNX CVS
> > > > > at Berlios:
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/freenx/nxc/
> > > > >
> > > > > The nxc code, though working well, is by
>
> > > far not
> > > > > finished, yet. There
> > > > > are many more features to be included, and
> > > > > weaknesses and some bugs
> > > > > to be fixed. Also, it needs to remain in
> sync
> > > with
> > > > > the ongoing work
> > > > > done by NoMachine's development team to
> enhance
> > > the
> > > > > NX protocol and
> > > > > add exciting new features to the NX
> technology.
> > > > >
> > > > > So volunteers to help with nxc development,
> > > > > documentation or promotion are
> > > > > welcomed by Lawrence.
> > > > >
> > > > > About the gNX project
> > > > > - ---------------------------------
> > > > >
> > > > > gNX ships two modules:
> > > > >
> > > > > 1) gnx -- A client written in python with
> a
> > > nice
> > > > > gtk gui in initial
> > > > > development stage.
> > > > > 2) thinnx -- A very thin GTK-1.2 client
> > > written in
> > > > > pure C for
> > > > > the ThinStation project.
> > > > >
> > > > > You can find the newest gNX source code in
> the
> > > > > FreeNX SVN repository:
> > > > >
> > > > > http://svn.berlios.de/viewcvs/freenx/
> > > > >
> > > > >
> > > > > About FreeNX
> > > > > - ---------------------------------
> > > > >
> > > > > The growing FreeNX Team does welcome anybody
> who
> > > > > wants to help with
> > > > > development efforts.
> > > > >
> > > > > * If you can't code, maybe you are good in
> > > writing
> > > > > documentation?
> > > > > * If you don't like to write documentation,
> > > maybe
> > > > > you like to do
> > > > > presentations and demonstrations of NX
> and
> > > FreeNX
> > > > > at your LUG,
> > > > > at a tradeshow, or at some Open
> > > Source/FOSS/Linux
> > > > > event?
> > > > > * If you don't like to appear on a public
> > > forum,
> > > > > maybe you could
> > > > > provide FreeNX developers with a remote
> login
> > > > > account on one of
> > > > > your systems, so we have a broader base
> for
> > > > > testing and bug
> > > > > hunting, as well as for demos and
> > > presentation?
> > > > > * If you don't have a publicly accessible
> > > > > Linux/Unix server, maybe
> > > > > you want to donate a small sum so we can
> rent
> > > a
> > > > > root server from
> > > > > a hosting provider?
> > > > >
> > > > > Thank you & Cheers,
> > > > >
> > > > > Fabian Franz
> > > > > Gustavo Noronha Silva
> > > > > Kurt Pfeifle
> > > > > Lawrence Roufail
> > > > > -----BEGIN PGP SIGNATURE-----
> > > > > Version: GnuPG v1.2.4 (GNU/Linux)
> > > > >
> > > > >
> > > >
> > >
> >
>
iD8DBQFCMdUJI0lSH7CXz7MRAmL6AJ96sDamZ+VnU2a3I8py4uCUjL+TsgCfYwfY
> > > > > eUcOPuN5H2Hy2qiK+WkUq44=
> > > > > =7n9p
> > > > > -----END PGP SIGNATURE-----
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > __________________________________
> > > > Do you Yahoo!?
> > > > Yahoo! Mail - Find what you need with new
> enhanced
> > > search.
> > > > http://info.mail.yahoo.com/mail_250
> > > >
> _______________________________________________
> > > > FreeNX-kNX mailing list
> > > > FreeNX-kNX at kde.org
> > > >
> https://mail.kde.org/mailman/listinfo/freenx-knx
> > > >
> > >
> > >
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Small Business - Try our new resources
> site!
> > http://smallbusiness.yahoo.com/resources/
>
>
__________________________________
Do you Yahoo!?
Yahoo! Mail - now with 250MB free storage. Learn more.
http://info.mail.yahoo.com/mail_250
More information about the FreeNX-kNX
mailing list