Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ rerun(1) — CX/UX 6.20

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

nice(1)

renice(1)

run(1)

memory(7)

mpadvise(2)

getpriority(2)

getquantum(2)

cache(7)

sched_get_priority_min(3p4)

sched_get_priority_max(3p4)

sched_getscheduler(3p4)

sched_setscheduler(3p4)

sched_getparam(3p4)

sched_setparam(3p4)

rerun(1)

NAME

rerun − alter execution environment of running processes

SYNOPSIS

/etc/rerun [-C cacheflags] [-b bias] [-c cpuid] [-m memflags] [ [-n nice] | [ [-s policy][-P priority] ] ] [-q quantum] [[-p] pid ...] [[-g] pgrp ...] [[-u] user ...]

DESCRIPTION

rerun alters the execution environment of one or more running processes.  The portion of the environment that may be altered includes

−C cacheflags
Sets the cache attributes of the processes to the given cache flags. Cacheflags is a comma-separated list of keywords specifying the cache mode to use for the stack and data regions.  Valid keywords are: copyback, writethrough, data_copyback, stack_copyback, data_writethrough, or stack_writethrough.  Note: For the specified processes, the old cache modes will still be used until a new program is invoked with exec(2).  All child processes created after the change will inherit the new cache modes. 

−P priority
Sets the priority of the processes. Priority is an integer value that is valid for the current scheduling policy of the process or, if the -s option is used, the specified scheduling policy.  Refer to sched_get_priority_min(3p4) and sched_get_priority_max(3p4) for information on determining the proper values.  max is also a valid priority value and will result in the processes running at the highest priority within the scheduling policy.  Only the super-user or a user with the ACC_SETPRI access vector can improve a process’s priority.  Higher numerical values represent more favorable scheduling priorities.  To change another process’s priority, the current real or effective user ID must match the real or effective user ID of the target process unless the current user is super-user or has the ACC_SETPRI access vector (if access vectors are configured).  This option cannot be used at the same time as the -n option. 

−b bias
Sets the CPU bias to the given mask.  Only the super-user or a user with the ACC_MPADVISE privilege can add processors to a bias.  Bias is a comma-separated list of CPU IDs or CPU ID ranges.  For example: "1,3-5,7". 

−c cpuid
Assigns the processes to the given CPU.  Only the super-user or a user with the ACC_MPADVISE privilege can change a CPU assignment. 

−m memflags
Sets the memory bindings of the processes to the given memory flags. Memflags is a comma-separated list of keywords requesting that some or all of a program be loaded into local memory. Valid keywords are: global, local, hard, text_local, data_local, stack_local, pcb_local, text_hard, data_hard, stack_hard or pcb_hard. 

−n nice
Sets process to the given nice value.  Only the super-user or a user with the ACC_SETPRI privilege can lower a nice value.  This option cannot be used at the same time as the -s option or the -P option. 

−q quantum
Sets the quantum to the given value.  Only the super-user or a user with the ACC_SETPRI privilege can increase a quantum. 

−s scheduling policy
Sets the scheduling policy of the processes. Valid keywords are: SCHED_FIFO, SCHED_RR, and SCHED_OTHER.  Refer to sched_setscheduler(3p4) and sched_getscheduler(3p4) for more information on scheduling policies.  The current priority of the process must be valid under the specified scheduling policy.  Otherwise, an error message will be returned.  To change another process’s scheduling policy, the current real or effective user ID must match the real or effective user ID of the target process unless the current user is super-user or has the ACC_SETPRI access vector (if access vectors are configured).  This option cannot be used at the same time as the -n option. 

The remaining options describe the collection of processes to be affected.  Arguments are interpreted as process IDs, process group IDs, or user names.  rerun’ing a process group causes all processes in the process group to be affected.  rerun’ing a user causes all processes owned by the user to be affected.  By default, processes are specified by their process IDs.  To force arguments to be interpreted as process group IDs, a −g may be specified.  To force them to be interpreted as user names, a −u may be given.  Supplying −p will reset the interpretation to be (the default) process IDs. 

EXAMPLES

The command /etc/rerun -n 1 987 -u daemon root -p 32 changes the scheduling priority of process IDs 987 and 32, and all processes owned by users daemon and root. 

The command /etc/rerun -c 3 -g 1456 moves process group 1456 to CPU 3. 

The command /etc/rerun -s SCHED_FIFO -P 21 -p 101 sets process 101 to run in the SCHED_FIFO (i.e. First-In-First-Out) scheduling policy with a priority of 21.

FILES

/etc/passwdto map user names to user IDs

SEE ALSO

nice(1), renice(1), and run(1). 
memory(7), mpadvise(2), getpriority(2), getquantum(2) and cache(7) for descriptions of memory flags, CPU bias, nice, quantum and cache attributes. 
sched_get_priority_min(3p4), sched_get_priority_max(3p4), sched_getscheduler(3p4), sched_setscheduler(3p4), sched_getparam(3p4), and sched_setparam(3p4) for descriptions of priorities and scheduling policies. 

CX/UX User’s Reference Manual

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026