Coding Guidelines/Safely Executing Other Processes: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 8: | Line 8: | ||
: in common-src/alloc.c | : in common-src/alloc.c | ||
Strip any unknown symbols from the environment. This protects the programs Amanda invokes from stray environment variables that might influence their operation. | Strip any unknown symbols from the environment. This protects the programs Amanda invokes from stray environment variables that might influence their operation. | ||
= safe_fd = | |||
: in common-src/file.c | |||
This function closes all descriptors execpt stdin, stdout, and stderr, and makes sure those three are open. Use this function when spawning a new process to ensure it isn't exec'd with any stray descriptors open. |
Revision as of 19:34, 22 May 2007
safe_cd
- in common-src/file.c
Change the current working directory to a "safe" location. This is necessary for a variety of reasons:
- Core files will be created in the working directory, so it should be writeable by the current user.
- The current directory of a process represents an open file on that filesystem, preventing it from being unmounted. Best practices dictate that long-lived processes should cd to / or a well-known location.
safe_env
- in common-src/alloc.c
Strip any unknown symbols from the environment. This protects the programs Amanda invokes from stray environment variables that might influence their operation.
safe_fd
- in common-src/file.c
This function closes all descriptors execpt stdin, stdout, and stderr, and makes sure those three are open. Use this function when spawning a new process to ensure it isn't exec'd with any stray descriptors open.