04-24-2011
I tried it too but it did not work as i want!!
![Frown Smilie](https://www.unix.com/images/smilies/frown.gif)
7 More Discussions You Might Find Interesting
1. Solaris
not sure what the problem is, when I go to /home and enter command mkdir i get this error
mkdir chris
mkdir: Failed to make directory "chris"; Operation not applicable
im root.... (3 Replies)
Discussion started by: csaunders
3 Replies
2. UNIX for Advanced & Expert Users
I want to know what i can set up so that root user can read everything. On my Solaris systems root can read the following directory.
drwxrwx--- 408 icsrc icarc0 36864 Aug 21 07:24 dev
drwxrwsr-x 7 icsrc icarc0 4096 Aug 4 1998 test
But on my linux systems it gets:
# cd dev
bash: cd:... (4 Replies)
Discussion started by: frankkahle
4 Replies
3. Shell Programming and Scripting
Hi all, i hope i got this in the right place, what i am trying to do is make a program only run by root, ie
for instance user fred is logged in and uses firefox, what id like to do is change that so that when fred wants to use firefox he will be asked to enter root password before he is allowed to... (14 Replies)
Discussion started by: dave123
14 Replies
4. UNIX for Dummies Questions & Answers
I want to build a Makefile that simply takes a template file and modifies it (sed or perl, probably) before installing the result in the right place - my problem is creating the variable for substitution...
So I have
SYSTEM = SYS1 SYS2
SYS1_CHANNELS = CHANNEL1 CHANNEL2 CHANNEL4... (1 Reply)
Discussion started by: JerryHone
1 Replies
5. AIX
dears,
good day.
i need to be able to take a mksysb for a machine running aix 6.1.5 without the root credentials and also without using sudo
any advice ? (2 Replies)
Discussion started by: islam.said
2 Replies
6. Cybersecurity
I stumbled upon this thread and one aspect of it got me thinking. As i am building a small Linux network right now for a friend i would like to hear your opinion on this.
I'd like to respectfully disagree. I think the Linux habit of disabling root login per default is wrong (not entirely... (6 Replies)
Discussion started by: bakunin
6 Replies
7. UNIX for Advanced & Expert Users
I have a series of configuration files to deliver to multiple unix environments (dev, test, bench, prod etc). However I don't to modify them for each environment.
The files are text which currently contain this type of directory information
IN=/DVT/ms/sas/reception/PIL_QPA_SID/GSPIN001... (5 Replies)
Discussion started by: clarcombe
5 Replies
LEARN ABOUT ULTRIX
renice
renice(8) System Manager's Manual renice(8)
Name
renice - alter priority of running processes
Syntax
/etc/renice priority [ [ -p ] pid ... ] [ [ -g ] pgrp ... ] [ [ -u ] user ... ]
Description
The command alters the scheduling priority of one or more running processes. The who parameters are interpreted as process ID's, process
group ID's, or user names. Using on a process group causes all processes in the process group to have their scheduling priority altered.
Using on a user causes all processes owned by the user to have their scheduling priority altered. By default, the processes to be affected
are specified by their process ID's.
Options
To force who parameters to be interpreted as process group ID's, a may be specified. To force the who parameters to be interpreted as user
names, a may be given. Supplying will reset who interpretation to be (the default) process ID's.
Users other than the superuser may only alter the priority of processes they own, and can only monotonically increase their ``nice value''
within the range 0 to PRIO_MIN (20). (This prevents overriding administrative fiats.) The superuser can alter the priority of any process
and set the priority to any value in the range PRIO_MAX (-20) to PRIO_MIN. Useful priorities are: 19 (the affected processes will run only
when nothing else in the system wants to), 0 (the ``base'' scheduling priority), anything negative (to make things go very fast).
Examples
The following command changes the priority of process ID's 987 and 32, and all processes owned by users daemon and root:
/etc/renice +1 987 -u daemon root -p 32
Restrictions
If you make the priority very negative, then the process cannot be interrupted. To regain control you make the priority greater than zero.
Non-superusers cannot increase scheduling priorities of their own processes, even if they were the ones that decreased the priorities in
the first place.
Files
Maps user names to user IDs
See Also
getpriority(2), setpriority(2)
renice(8)