Dnet client on Linux questions

[striker64]

I've got the dnet client running as a background process on my linux machine (dual Cel 400's @500), and I'm using the following line in my startup file:

/home/mike/dnetc -noquiet >> /dev/tty8 &

which works fine. However, I have a couple of questions. First of all, If I press Alt+Ctl+F8 in X, it displays the program output, but I can't for the life of me figure out how to get back to my desktop without restarting the X server?

The other question I have is: Is there any way to see the program output when logged in remotely using telnet or ssh? I can check the 2 processes to make sure they are both running, but it would be nice to check how many units have been completed.

Mike

 

[SyZ]

A good alternative if you want to look at the client from other than just the console is screen.

screen ./dnetc -noquiet

.. will start the process. Pressing ALT-A then D will detach the screen, keeping the client running.

screen -rD
... will detach the client from whatever was looking at it and let you view it (via telnet or console or however) just like you had run it initially from that terminal. You can lose your connection to the machine ungracefully (i.e. lost dialup connection) and the client will remain active.

I keep my pproxy and all clients screened off like this, that way I can see everything in real time, but never have to shutdown the process or disrupt anything.

Another way to view the client is to just activate logging to a file on your machine, then run tail <filename> to view the last 10 lines or so.



- SyZ

 

[Christoph]

You should be able to get back to your X session with Ctrl-Alt-F(1 + max virtual consoles).

Usually (at least for Red Hats I've used lately) that's Ctrl-Alt-F7. If not, just try 'em all.

As far as seeing the output from another machine, you could:
- configure the client to use a logfile, then view (vi, cat, tail,...) the logfile
- redirect the output to a file instead of a tty, then view the file remotely
- start the process with nohup, ie:
nohup /home/mike/dnetc &amp;
then view the resulting nohup.out file.

I tend to set up a log file, and start it with nohup.

-Christoph