hi John, in principle, --detach could have this option -- however, this also means that --detach would no longer produce a full UNIX daemon if additional non-default value is given. For the reasons of clarity, I'd personally leave --detach for strict "daemonization", and rather use the following approach for starting SEC if the working directory must remain the same:
sec.pl ... >/dev/null 2>&1 & (Logging out would probably send SIGHUP to SEC process, but if you log out immediately after starting the process, that would not be a big issue?) As an additional remark, I'd personally use absolute paths for file names in command lines, unless I am testing something on a temporary basis. kind regards, risto On 02/20/2010 12:50 AM, John P. Rouillard wrote: > Hi all: > > I wanted to start a sec process as myself and logoff. I figured this > would be a perfect reason to use the detatch option. However detatch > also changes the directory to /, and all relative references to files > on sec's command line are done with respect to /. > > I understand the reason is to allow the filesystem where the user > started sec to be unmounted but if you are on a local filesystem it is > unlikely to be unmounted unlike an automounted nfs share. > > Might I suggest a -workingdir option to specify the directory that > -detach will change to. > > (I was originally thinking of -detach[=working directory] but the way > options parsing is set up the -workingdir is probably easier.) > > Risto comments? I could probably generate the patch as well, it should > be simple enough to be within my capability. > > In any case off to get a command line with nohup and all the fd > redirection operators set up. > > -- > -- rouilj > John Rouillard > =========================================================================== > My employers don't acknowledge my existence much less my opinions. > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Simple-evcorr-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Simple-evcorr-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users
