Haehnel and Adams:
Thanks a lot for your reply and help.
In fact what I want to do is use "john" to crack the passwd file of my
computer to see if my users have set it safe.
After check again, I find your ways about let the program run background is
good. And after logout and login back again, checking with top show that it
is still run happily there. But I don't know why run "ps -a " will not give
me this effect. It is strange that it shows process such as X are running
while don't report the existence of "john".
But again, I don't know what to do? After login again, how to make my
program jump to the foreground?
many many thanks.
I love this board.
Robert Haehnel wrote:
> Maybe I'm missing something, but I cannot believe that this is as
> difficult as it is being made out to be. I do this all the time with
> computationally intensive programs. Simply let it run in background by
> putting the ampersand after the command e.g.
>
> myprogram &
>
> or
>
> ./myprogram &
>
> if . is not in your path. The fact that it is so easy to do this is the
> main reason I switched from NT to Linux. That and the fact that I can
> remotely log in and restart jobs from home or on the road. Try that in
> NT! Unix is the environment where real work gets done. If your program
> sends stuff to STDOUT (i.e. the screen) and you want to see all of that
> later then
>
> myprogram > screendump &
>
> then all of the screen output will be dumped into a file called
> screendump for your later review.
>
> Regarding not finding the process in ps. Well, you won't find it there,
> 'cause ps shows processes that are running that were started by the
> terminal you are currently logged into (a little know fact). To prove it,
> while in X, log into two xterms. From one start a program in background
> (e.g. emacs &). Now from that xterm type ps. There is emacs listed. Now
> run ps from the other xterm. Huh? emacs isn't found. Now run top. Ah Ha,
> there is emacs.
>
> There may be a switch that allows you to use ps to see all processes
> started by you (your username) but off the top of my head I wouldn't know
> what it is. You should be able to see your process in top though. That
> shows all of the processes running on the machine. That list will be much
> longer, but it should be in there (provided it didn't finish running
> while you were away).
>
> Happy computing
>
> LordX wrote:
>
> > My application needs to run all day long even after I log out ( yes, I
> > don't want to log into the computer all day long. :)
> > What should I do to let my program continue runing after my log off?
> > Thanks
>
> --
>
> Robert B. Haehnel
> Ice Engineering Research Division
> Cold Regions Research and Engineering Laboratory
> 72 Lyme Road
> Hanover, NH 03755-1290
>
> Phone: (603)646-4325
> Fax: (603)646-4477
> e-mail: [EMAIL PROTECTED]
> web: http://www.crrel.usace.army.mil
