The "cgi-bin" directory does not exist until you create it with your FTP program at the top level of your website directory. Any files you place in it will be treated as programs (instead of HTML pages or images), and will be "run" by the server instead of displayed normally. The "cgi-bin" directory is the location you will use to store your Perl or compiled script files. So what is the "cgi-bin" directory, anyway?
If you install any scripts, you may need to know the location (path) of your "cgi-bin" directory on the server's disk. Windows installers don't expect such a thing, and won't put files there automatically the way that Linux installers will usually do.To see a more detailed answer customized for you, type your domain name here: Of course, you'll have to add files / scripts / shortcuts / symlinks to your bin directory yourself. Windows combines the per-user and system-wide PATH environment variables, so anything in the machine PATH variable is also added to any user's PATH, but not the other way around. For a per-user location, create the directory in your own profile ( %USERPROFILE%\bin) and add it to your account's PATH environment variable. To make it system-wide, place it somewhere like the root of the file system (as in C:\bin) or under an already-restricted location like \Windows\System32\bin), and add it to the PATH environment variable for all users. You can easily create your own equivalent of /bin on Windows. As Ryan says, the \Windows\System32 directory on Windows is also in PATH for all Windows users (and, even if it isn't, Windows' program loader will search there anyhow). It's just the location where executable files (including scripts, which aren't actually binary files) are placed by convention, and it is included in the PATH environment variable by default for all users. There's nothing actually special about /bin on Unix/Linux at all.
0 kommentar(er)
