Most users should not have to edit any configuration files manually. However, in some cases you might have to supply some information about akwardly placed include files/libraries or you might want to explicitly disable building some of the optional PDL modules. Check the files INSTALL and perldl.conf for details. If you had to manually edit perldl.conf and are happy with the results you can keep the file handy for future reference. Place it in ~/.perldl.

PDL files should be kept in a directory at the same level as the SQL and src files. If the PDL does not contain any database specific queries (e.g., something containing a connect by statement) then it should end in (.pdl). Otherwise, you should create a copy of the query for each database and name each copy appropriately: .ora.pdl for Oracle or .pg.pdl for PostgreSQL.

Unix text files (often called "plain text" files, or "ASCII" files) can be edited with any text editor that can save files in "plain text" format (i.e. without any special formatting or fonts, etc). Another requirement for a text editor for Unix text files is that it save files using the standard Unix convention for end-of-line characters.

Just installing Webmin will not cause any config file changes to be made. When you start to use it, only the config files related to the changes that you make in Webmin will be modified. For example, using the Apache Webserver module would not effect your Sendmail configuration. If you are using SSL, make sure you connect to a URL like https://myhost:10000/ instead of http://myhost:10000. Without the https, your browser won't use SSL mode and thus will display this error.

Good question. If you are editing your own personal site in your public_html folder, you can put any legal content in there you want.(If you put any illegal content in your folder, you assume responsibility for any penalties that may occur.) If you are editing a departmental or organizational site, however, there are some more limitations. Specifically, if you are creating or redesigning the site, it should use the new WOU website template.

Right-click one or more tracks, choose 'Properties' from the context menu. Various additional functionality can be accessed by selecting one or more fields in the Properties dialog and right-clicking them. Note that you can mass-edit tags of a group of track by opening the Properties dialog on multiple items. No. If you want to edit tags of multiple tracks, you can do it more efficiently by just selecting them all and opening the Properties dialog for them.

Yes. In versions prior to 0.7.1, you can start colinux with colinux-daemon.exe -c c:\pathTo\other.colinux.config substituting the name of your configfile for c:\pathTo\other.colinux.config. In versions 0.7.1 and later, you use colinux-daemon @c:\pathTo\other.colinux.conf. You can then create .bat files or shortcuts with this command for easy click-and-run starting of various setups. edit] Q16.

PDL stands for Perl Data Language . To say it with the words of Karl Glazebrook, initiator of the PDL project: The PDL concept is to give standard perl5 the ability to COMPACTLY store and SPEEDILY manipulate the large N-dimensional data sets which are the bread and butter of scientific computing. e.g. $a=$b+$c can add two 2048x2048 images in only a fraction of a second.

The complete PDL documentation is available with the PDL distribution. If you have PDL installed on your machine and are on a unix like system then you can read the PDL manuals with the man command. man PDL::Intro will lead the way to other PDL manual pages. In any case (i.e. also on non-unixes) perldoc PDL::Intro should work. The easiest way by far, however, to get familiar with PDL is to use the PDL online help facility from within the perldl shell. Just type perldl at your system prompt.

Yes, as of December 1999, PDL is available at the CVS repository on http://www.sourceforge.net . The tree is updated by developers who have accounts on Sourceforge and snapshots of the tree are released regularly by the pumpkin holder (the pumpking).

null is a special token for 'empty piddle'. A null pdl can be used to flag to a PDL function that it should create an appropriately sized and typed piddle. Null piddles can be used in places where a PDL function expects an output or temporary argument. Output and temporary arguments are flagged in the signature of a PDL function with the [o] and [t] qualifiers (see next question if you don't know what the signature of a PDL function is).

AYou only have to edit the myPh3.config.php file and fill in your site url (the subdirectory the script is running in), your image directory (not within your website for security) name, description and welcome message. It's commented and speaks for itself. If you like, you can also change settings like language, enable url rewriting, thumbnail size, visual style, acceptable filetypes, etc.

When I open the PageKit in my web editor, it says "You are not using a frames compatible browser". What is going on?!

MaxDB has several configuration files. To locate the files use the information given in Which logfiles exist?.

Special Thanks to Daniel Rackerby for the feedback and contributions to the FAQ. Back to: Mac OS X-IP Setup

There are two places AfterStep configuration files could be. The global directory is usually /usr/local/share/afterstep/ (unless you installed from a binary package, or specified a different place). All configuration files should be here, and really shouldn't be edited. The preferred method for changing your configuration is copying the file you wish to change to ~/GNUstep/Library/AfterStep/, the personal configuration file directory.

The switch allows up to three startup-config files with options for selecting which startup-config file to use for: A fixed reboot policy using a specific startup-config file for a specific boot path (primary or secondary flash) While you can still use remote storage for startup-config files, you can now maintain multiple startup-config files on the switch and choose which version to use for a reboot policy or an individual reboot.

Latest Answer: saswata.purkayastha you are correct. We can can have one web.config file in each different directori...

After upgrading, FireWall-1 loses its state, so you must start the GUI and install the Security Policy.

bash_profile and ~/.bashrc are the two main config files for bash. At the top of .bash_profile the STWing.bash_profile is brought in first. These are the system settings and is updated by the Sysadmin staff, please do not remove it. Add all your changes after that line. note: some examples of these files are included in the Appendix Section A: Supplements. They are for reference, and are simply my way of setting things up. They should only be taken as a guide.

The output of pnpdump should give you the examples you need for your hardware. If you run it with the -c (--config) flag, it should even show how to configure your hardware in the output. The output of pnpdump is supposed to be used as the input to isapnp after editing.

The user's global configuration files of Chamo are stored in the ~/.cameleon2/ directory and are prefixed with "chamo.". The files are created if they don't exist. They are human readable with an OCaml-like syntax. There are also "local" configuration files, that is files stored in the directory where Chamo was launched. By now, we can find: chamo.sourceview.

nodemap.cfg: This file contains the primary IPs of all the nodes in the cluster. This is a required file, without this RainWall will not work. vip.cfg: All of the VIP pools are listed in this file; this file should be identical for all the nodes in the cluster. This is a required file, without this RainWall will not work. localmonitor.cfg: This file gives the administrator detailed control of the different kinds of local fault monitors available.

The PORTUS CD contains an OS/PORTUS/examples directory, where OS can be either AIX, Linuxx86, or Solaris.

The configuration files are used to set environment variables in EMS-2. As functionality is added, oftentimes an environment variable may also need to be added. It may not be necessary if you are developing to functionality requirements from the previous version, but you should keep in mind that a later update to your project may include the most current version of EMS-2. Bottom line, overall configuration management of your EMS environment should reflect the newest and most current tools.