COSmanager User Man pages
From Documentation
Contents |
asgroup
NAME
- asgroup — Run a program with another group's permissions
SYNOPSIS
- asgroup <group> [<command>]
DESCRIPTION
- Asgroup changes the effective group ID of the user to the specified group while running command. If no command was specified, an interactive Shell will be started, either using the program defined by the SHELL environment variable, or /bin/sh if SHELL is not defined. Asgroup will only permit execution to proceed if either:
- The user is part of the specified group; or
- The command's group is the one specified, and it has the set group ID bit enabled [see chmod(1)], and the user has execute access to the command.
All attempts (both successful and not) are logged to an audit trail.
FILES
- /usr/spool/log/asgroup
- Audit log file. Every execution of asgroup is logged here detailing the user, terminal, date andtime, the command and whether it was successful.
SEE ALSO
- fs_tools(1).
COPYRIGHT
- Copyright © 1990-2006 Functional Software. All rights reserved.
asuser
NAME
- asuser - Run a program as another user
SYNOPSIS
- asuser [-12cdosu] <user> <command>
DESCRIPTION
- Asuser runs a command in the context of another user. It is normally only run by a process with the effective user ID of the superuser.
- Switching to the specified user causes the process to switch to that user's ID and Groups, plus the following environment variables to be set: LOGNAME, USER, HOME and FULLNAME.
OPTIONS
- -c
- Check that the caller's effective ID is superuser before running the command. By default, if the caller is not superuser, the command is still run, but without switching users.
- -d
- Change into the user's home directory before running the command, and before creating any output files (see the -o, -1 and -2 options). Normally the command is run in the current working directory.
- -s
- Run the command using the shell. This allows arbitrary shell syntax to be used in the command. Normally the command must be a single program name, optionally followed by its parameters.
- -u <ulimit>
- Set the ulimit to the specified value prior to running the command.
- -o <file>
- Redirect both STDOUT and STDERR to the given file after switching to the new user. If the file does not exist, it will be created with the ownership of the given user. Note that if you use:
- asuser <user> <command> > <file>
- the file will be opened by the shell prior to running asuser, causing it to be created with "root" ownership.
- -1 <file>
- Redirect STDOUT to the given file after switching to the new user. Please refer to the discussion under -o.
- -2 <file>
- Redirect STDERR to the given file after switching to the new user. Please refer to the discussion under -o.
EXAMPLE
- asuser mike weekly_report -d prodn
- Runs the command "weekly_report -d prodn" as user "mike".
WARNINGS
- This program must not be installed with the SETUID flag set, otherwise system security would be compromised.
COPYRIGHT
- Copyright © 1990-2006 Functional Software. All rights reserved.
audcycle
COPYRIGHT
- Copyright © 1990-2006 Functional Software. All rights reserved.
audit
COPYRIGHT
- Copyright © 1990-2006 Functional Software. All rights reserved.
audview
COPYRIGHT
- Copyright © 1990-2006 Functional Software. All rights reserved.
browser
COPYRIGHT
- Copyright © 1990-2006 Functional Software. All rights reserved.
cos
COPYRIGHT
- Copyright © 1990-2006 Functional Software. All rights reserved.
daemon
COPYRIGHT
- Copyright © 1990-2006 Functional Software. All rights reserved.
fs_tools
NAME
- fs_tools - the Functional Toolset
SYNOPSIS
- The Functional Toolset is a suite of tools, to enable sophisticated applications to be built quickly and easily. It consists of a suite of user interface tools, database access tools, and various miscellaneous tools. The Functional Database tools are described under db(1). This manual page describes the user interface tools, the environment variables that the toolset uses, and some common facilities which the toolset uses (such as path lists).
USER INTERFACE TOOLS
- These are full-screen, interactive programs, each with a distinct function and they support both a Graphical User Interface (GUI) and a Character User Interface (CUI), the latter can run on virtually any terminal.
- These functions include:
- Picking an item from a menu
- Filling in a form
- Browsing through output, and optionally printing sections
- Choosing one or more items from a list
- Hitting one of a number of function keys in answer to a request
- Although these functions are implemented as separate programs, the "look and feel" of each of the tools is the same, so the user interface remains uniform throughout an application built with these tools.
- Below are brief descriptions of the functions and features of each user interface tool. Further details can be found in the appropriate manual entry for each.
MENU
- Menu implements a hierarchical menu structure. The user simply arrows down to the desired item, and hits Enter or Accept. If that item is an action then the program corresponding to that action is executed. If it is a submenu, then that menu will be entered. Hitting Exit will take the user up a level in the menu hierarchy, or exit Menu completely if it was the Main or Top-level menu.
COPYRIGHT
- Copyright © 1990-2006 Functional Software. All rights reserved.
menu
COPYRIGHT
- Copyright © 1990-2006 Functional Software. All rights reserved.
methtool
COPYRIGHT
- Copyright © 1990-2006 Functional Software. All rights reserved.
page
COPYRIGHT
- Copyright © 1990-2006 Functional Software. All rights reserved.
root
COPYRIGHT
- Copyright © 1990-2006 Functional Software. All rights reserved.
runopt
COPYRIGHT
- Copyright © 1990-2006 Functional Software. All rights reserved.