code_saturne(1) [debian man page]

CODE_SATURNE(1) 					       Code_Saturne commands						   CODE_SATURNE(1)

NAME

       code_saturne - Main user script of Code_Saturne.

SYNOPSIS

       code_saturne [-h|--help] <command>

DESCRIPTION

       The code_saturne script is the main user script of Code_Saturne.

OPTIONS

       -h, --help
	      Help message.

COMMANDS

       Further information will be obtain with code_saturne <command> --help

       check_consistency
	      The  code_saturne  check_consistency command checks the consistency between the user files and the Xml file (from the Graphical User
	      Interface) provided by the user and, if needed, that the chosen options are compatible with parallel calculations. Lastly, it prints
	      the chosen specific physics.

       check_mesh
	      The  code_saturne  check_mesh  command verify the quality of a given mesh. The following options will be passed to Code_Saturne pre-
	      processor.

       compile
	      The code_saturne compile command can be used to generate the cs_solver executable needed for running a Code_Saturne study.

       create The code_saturne create command sets up a directory structure for a Code_Saturne study or case. The  different  directories  created
	      are  MESH  for meshes, POST for user post-processing and a case directory (or several) containing a DATA, SRC (to store user files),
	      RESU (to store results) and SCRIPTS directory.

       info   The code_saturne info command is a wrapper for an easier look at Code_Saturne documentation.

SEE ALSO

       cs_io_dump(1), cs_partition(1), cs_preprocess(1), cs_solver(1)

								    2009-10-27							   CODE_SATURNE(1)

SETUID(1)						      General Commands Manual							 SETUID(1)

NAME

       setuid - run a command with a different uid.

SYNOPSIS

       setuid username|uid   command [ args ]

DESCRIPTION

       Setuid  changes	user id, then executes the specified command.  Unlike some versions of su(1), this program doesn't ever ask for a password
       when executed with effective uid=root.  This program doesn't change the environment; it only changes the uid and then uses execvp() to find
       the command in the path, and execute it.  (If the command is a script, execvp() passes the command name to /bin/sh for processing.)

       For example,
	      setuid  some_user  $SHELL
       can be used to start a shell running as another user.

       Setuid  is  useful  inside  scripts that are being run by a setuid-root user -- such as a script invoked with super, so that the script can
       execute some commands using the uid of the original user, instead of root.  This allows unsafe commands (such as editors and pagers) to	be
       used  in  a  non-root  mode inside a super script.  For example, an operator with permission to modify a certain protected_file could use a
       super command that simply does:
	      cp protected_file temp_file
	      setuid $ORIG_USER ${EDITOR:-/bin/vi} temp_file
	      cp temp_file protected_file
       (Note: don't use this example directly.	If the temp_file can somehow be replaced by another user, as might be the case if it's kept  in  a
       temporary  directory,  there  will  be a race condition in the time between editing the temporary file and copying it back to the protected
       file.)

AUTHOR

       Will Deich

								       local								 SETUID(1)