02-06-2007
The nice command
hello everybody:
I have some job running on tru64 system and Im the root, due to limited resources I end up with my job ( vdump) for example taking the lowest share, I researched the nice command on the net, but couldnt get enough info, can I use it to already running process or I only use it while launching the job.
can I use it to add the priority to all certain user's processes or just to one process at a time ??
and what are the best options to use wth that command.
Thanks alot guys.
10 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
Just a quick message to say great work to Neo and any others who have helped with the upgrade - the layout, appearance and functionality of this forum ROCKS.
By far the best I have seen.
Excellent! (1 Reply)
Discussion started by: alwayslearningunix
1 Replies
2. UNIX for Dummies Questions & Answers
Can someone tell me .. how to find a user & process who has executed nice (scheduled priority) to one of his process. .Tks.. (5 Replies)
Discussion started by: sivan
5 Replies
3. UNIX for Advanced & Expert Users
Under, Solaris 10 I have the following problem:
A script executed at command line runs with nice level 0, as expected.
Same script started under (user) crontab runs with nice level 2.
I would prefer it run at 0. Is this possible? If so, how?
Thanks. (0 Replies)
Discussion started by: henrydark
0 Replies
4. UNIX for Dummies Questions & Answers
Can someone tell me this. thanks (1 Reply)
Discussion started by: xoxouu
1 Replies
5. Programming
Hi I want to implement the nice command in the shell that I am building. I came to know that there is a corresponding nice() system call for the same. But since I will be forking different processes to run different commands typed on the command prompt, is there any way I can make a command... (2 Replies)
Discussion started by: tejbuch
2 Replies
6. UNIX for Advanced & Expert Users
Hello,
Some guy said to me that using the nice command to decrease the priority of a process is a myth, that the operating system corrects the priorities as the processes need cpu. Is this true? (4 Replies)
Discussion started by: psimoes79
4 Replies
7. Shell Programming and Scripting
Hello,
I am just starting with shell scripting, as everyone will soon see from my question. What I'm trying to do is call the Nice command to set the script process priority from /bin/ksh. The difference is I'm running it not directly through the shell, but through Bigfix (very similar to... (3 Replies)
Discussion started by: solly119
3 Replies
8. Shell Programming and Scripting
Dear Friends,
I have a directory when i take du of that directory it takes alot of memory and cpu and I/O, i want to use nice to run my script that have du command slowly so it won't take I/O and cpu, please suggest. (6 Replies)
Discussion started by: learnbash
6 Replies
9. BSD
Hello Folks,
Recently our FreeBSD 7.1 i386 system became very sluggish.
Nothing much is happening over there & whatever is running takes eternity to complete.
All the troubleshooting hinted towards a very high nice percentage.
Can that be the culprit?
Pasting snippets of top command,... (7 Replies)
Discussion started by: vibhor_agarwali
7 Replies
10. Shell Programming and Scripting
with using wall command, how can i have a carriage return in my broadcast message. i try to broadcast from a file, i were to use "cat myfile | wall" for broadcasting. but when the message broadcast somehow the format run away.
this the text in my file:
line 1
line 2
line 3
when broadcast
... (3 Replies)
Discussion started by: lsy
3 Replies
LEARN ABOUT SUSE
vm-install-jobs
vm-install-jobs(8) System Manager's Manual vm-install-jobs(8)
NAME
vm-install-jobs - queries and manages VM creation jobs that were started by vm-install
SYNOPSIS
vm-install-jobs [options ...]
DESCRIPTION
VMs may be created by vm-install interactively, or as backgrounded jobs. The vm-install-jobs command manages backgrounded VM creation
jobs.
OPTIONS
--cancel job-id
Cancels the specified job. If the VM is still running, it is stopped. This command may return before the VM is completely stopped
or the vm-install process has completely exited. The job is not implicitly deleted, so that the cancelation progress may be
observed.
--delete job-id
Deletes the specified job. The job must be in one of the FINISHED, FAILED, or CANCELED states. The VM's configuration is deleted,
as are any disks that were created during the job.
--detach job-id
Detaches the created VM from the specified job. The job must be in the FINISHED state. The job is deleted, but the VM's configura-
tion and its disks are left intact.
--list Lists all known VM creation jobs, by ID. One job ID is output per line.
--status job-id
Outputs the status of the specified job.
JOB STATES
Every job is always in one of the following states:
0: SETTINGS
1: PREP_INSTALL
2: INSTALL
3: POST_INSTALL
4: RUNTIME_CONF
5: RUNTIME
6: FINISHED
7: FAILED
8: CANCELED
The normal progression is from state 0 to state 6. States 6, 7, and 8 are terminal states.
JOB STATUS
Querying the job status will print (to stdout) a number of key/value pairs. The possible keys and their meanings are:
exit The exit code of the VM creation job. This key is only present once the job is in one of the states FINISHED, FAILED, or CANCELED.
To interpret the meaning of the exit code, see vm-install(8)
id The job ID. Always present.
inotify
A filename to monitor (via inotify(7) ) for state changes. The recommended inotify mask to use is IN_CLOSE_WRITE. Always present.
log The location of the log file. Always present.
pid The process ID of the VM creation job. This key is only present if the VM creation process is still running. The PID is used
internally to cancel the job.
state The job's current state. See JOB STATES. Always present.
uuid The VM's UUID. This key is only present once all of the VM's settings have been gathered.
vnc The last known location to view the VM's console via VNC. Note that the presence of this key does not guarantee that the VM is cur-
rently running. When no authentication is necessary, the URL will be ip::port. If authentication is necessary, the URL will be
username:password@ip::port.
DIAGNOSTICS
A zero exit code indicates success; non-zero indicates failure.
Note that the exit code of this tool indicates the success of the job management command. It does not represent the success or failure of
the job itself.
SEE ALSO
To interpret the exit code of a job or of this command, see vm-install(8)
To monitor state changes of jobs, see inotify(7)
To report problems with this software or its documentation, visit http://bugzilla.novell.com
2007-02-01 vm-install-jobs(8)