Answer: In menu "Options" - "TroubleShooting", press the button "Export Configuration" to get the file.

There is a no such thing as THE config file for a particular card or monitor. The XF86Config file you should use is dependent on your card, monitor, operating system, mouse, keyboard, individual preferences, network setup, available fonts, etc. It is not a good idea to exchange XF86Config files. While it may be safe to use certain parts of another's config file, in general, you are better off generating your own.

SpamBayes looks for your configuration file in three places - if it can't find it, then, obviously, your options will not be loaded. The first place that SpamBayes checks is the environment variable BAYESCUSTOMIZE. You can set this to the path of your configuration file, wherever it is, and it will be loaded. You can also specify more than one file, separated by the appropriate path separator for your platform.

Information on the new changes can be found in a REC published leaflet.

Answer: It's a security feature, to prevent users on other systems from using your host as a "counter server". For information on automatically recognising new virtual hosts as they're added, see the answer to question 9. (Contributed by: Sean Reifschneider jafo@gateway.tummy.com)

Could you give the user the flexibility to change just the real important things rather than everything? >I took a look at tkbiff and it looks very nice. For the novice user, the >configuration file looks a bit overwhelming. If somehow the code could be >stripped out and just leave the user to change the real important things >would be nice. I actually wrote another biff which was vastly simplified. But simplicity has substantial drawbacks.

Yes. The DOMConfigurator supports automatic reloading through the ConfigureAndWatch APIs. See the API documentation for more details.

Most form->email handling scripts are controlled by fields hidden in the form. However, because of this, people can call the script from anywhere on the web, using their own forms. Obviously, this sort of freeloading isn't very polite, and needing to use a configuration file stops people doing this, because it means they must have write access to the webserver. There is also the issue of the order that configuration statements are run.

This problem USUALLY means that your IFS Home Directory is over its quota. You can check this with the command: If you're "Used" portion is more than your "Quota" portion, then you are over your quota. You'll either have to make your quota larger ('lynx http://www.ifs.umich.edu/~ifs'), or delete some files to fix the problem.

The default init scripts do not start mvpmc. Instead they try and tftp a config file from your tftp server. This allows you to modify your use of mvpmc without rebuilding the dongle.bin file. It also allows you to easily have different configurations for different MediaMVPs in your network. This config file is the name of your dongle.bin bootfile, with .config appended to it (ie, dongle.bin.config).

Athens was developed for UK Higher Education market, so many resources do not use it. Instead we use EZproxy to provide access to those resources. Our EZproxy server is on campus, and we route our links to IP-authenticated resources via EZproxy. Once you have logged in to the EZproxy server it downloads web pages for you and then relays them to you.

You will be asked during the installation whether you would like keep your existing configuration or overwrite it with a new configuration.

Yes. Both the DOMConfigurator and the PropertyConfigurator support automatic reloading through the configureAndWatch method. See the API documentation for more details. Because the configureAndWatch launches a separate wathdog thread, and because there is no way to stop this thread in log4j 1.2, the configureAndWatch method is unsafe for use in J2EE envrironments where applications are recycled.

Yes, the Config Files are not removed when you un-install a program. They will still be in the Program Files directory in your C Drive. Just browse to the Config File folder that was created for the original program and select your Config Files. The new program will "copy" each Config File to the Config File folder in the new program as you select each one.