--- Marc Krawitz <[EMAIL PROTECTED]> wrote: > Here are the parameters for the NULL device. Is the VOLUME SET(CPU) > supposed to be blank? Anyone see any other problems? > > Thanks, > If you look at the field description (Data Dictionary Utilities), you will see tht leaving this field blank means the device is accessible from any volume. This is probably what you want. I don't know about GTM, but if Cache' is configured to run in a clustered environment, then you may hava device that should only be used by processes running on a particular CPU.
You should only have one entry for a NULL device, though. The problem is that if you specify a device as "NULL" and that string doesn't uniquely identify a device, then the call can fail, and tasks tied to the device will not run. Does that sound mysterious? Think about using NULL as a mehod of simulating the behavior of a daemon process (e.g., disassociating it from the controlling terminal). There are other ways of doing it, of course, but what you're seeing is the VistA equivalent of $ acommand > /dev/null & entered at the bash prompt. If "acommand" produces output (or may do so) but you still want to run it in the background, you can just redirect the output to /dev/nul and run it in the background with "&". (Real daemon do something else to arrange for there to be no controlling terminal. I can go into it if you want me to.) === Gregory Woodhouse <[EMAIL PROTECTED]> "If you give someone Fortran, he has Fortran. If you give someone Lisp, he has any language he pleases." --Guy L. Steele, Jr. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
