I've managed to get both the binary solaris release of ast-ksh (2008-02-??) and today's latest release built from CVS (2008-11-04) into a state where the "jobs" alias consistently returns garbage, and I'm trying to figure out how it gets into this state - any suggestions ?
Here is the problem : Every time I run any command, it gets added to the jobs list, even if no command is actually run, let alone in the background: $ env ... $ josb /home/cmob/bin/sol10.sun4/ksh: josb: not found [No such file or directory] $ jobs [3] + Running josb [2] - Running env [1] Running env $ jobs [4] + Running jobs [3] - Running josb [2] Running env [1] Running env $ job /home/cmob/bin/sol10.sun4/ksh: job: not found [No such file or directory] $ jobs [6] + Running job [5] - Running jobs [4] Running jobs [3] Running josb [2] Running env [1] Running env $ jobs [7] + Running jobs [6] - Running job [5] Running jobs [4] Running jobs [3] Running josb [2] Running env [1] Running env $ jobs [8] + Running jobs [7] - Running jobs [6] Running job [5] Running jobs [4] Running jobs [3] Running josb [2] Running env [1] Running env It even does this when I move: $ mv ~/.kshrc .not-kshrc $ mv ~/.login .not-login $ mv ~/.profile .not-profile But I'm sure it did not do this before I started playing around with these files. There are several real large 'nohup' jobs going on - it does not get into this state before I initiate large nohup jobs. Once in this state, it does not get out of it until my nohup jobs are complete. Is there some setting that could account for such behaviour ? Any ideas anyone ? Any help on this would be much appreciated . Thanks & Regards, Jason <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
_______________________________________________ ast-developers mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-developers
