Made some progress, however after reading through previous posts on this subject I found that I can simply add the chroot command into the /etc/passwd file
I am assuming that there needs to be a /bin directory (which originally would be located in /vol/mita/test/bin/) with the csh command in the directory. However, when I try to su "user", I get an error that says "no shell".
Any ideas? Am I implementing this command correctly?
restricted access...
Hi
I need to restrict users shell access to only $HOME under /home for each user. I don't want them getting out of their own directories. From what I understand chroot is something I could use, but I want to avoid this since it involves creating symbolic links to a number... (9 Replies)
I have a need to allow only certain IP addresses to access a machine running solaris 9. I am not sure how this can be accomplished.
Thanks in advance for your help.
Patch (2 Replies)
Hi All,
I'm on Solaris 8, I need to provide Read-only access to a user to 2 directories only.
Using rsh (restricted shell) as the user's login shell, I can restrict the user's access to a certain directory only, but how can I set in such a way that the user can access only the 2 directories... (4 Replies)
I'm the admin in a shop in which my developers have and use the root account, all UNIX newbies.
I've been unable to convince management myself that this is an unacceptable practice.
I've looked in a couple books I have and can't find any chapters, discussions, etc that make the argument that... (2 Replies)
We want to secure access to a server by restricting the number of users who can login to it. Our users are NIS users. Only few of them can telnet/ssh this server.
Do you have any idea on how to implement that?
thanks. (1 Reply)
Hi All,
I am facing a problem, regarding code security on a server.
We have configured a server which contains our code (ear present in jboss/server/xyz/deploy) in it, and need to bind the code to the server itself so that no one can take the code out of the. the problem is that the password of... (3 Replies)
Dear All,
I have created a user called "x" who is allowed only to FTP and it is working fine. Here my problem is, I want to give access to a particular directory say for eg:- /dump/test directory. I don't find any option in the useradd command to restrict access to this particular directory only... (1 Reply)
Hi all.
I've had a quick look around but cant see anything exactly matching my requirements.
I have a new T2000 running S10. Im looking to restrict the no. cores that a S10 non-global zone can use to 1 only. The box is single CPU but 8core.
I want to do this to save on some software... (4 Replies)
Hello,
I am using MySecureShell to chroot all sftp accesses. The problem that I have is that my boss does not want root to be able to use sftp. Root should still be able to ssh. Any ideas? (2 Replies)
Dear all,
I am administering a DC environment of over 100+ Solaris servers used by various teams including Databases.
Every user created on the node belonging to databases is assigned group staff(10) .
I want that all users belonging to staff should NOT be able to execute certain system... (6 Replies)
Discussion started by: Junaid Subhani
6 Replies
LEARN ABOUT OPENSOLARIS
nice
nice(1) User Commands nice(1)NAME
nice - invoke a command with an altered scheduling priority
SYNOPSIS
/usr/bin/nice [-increment | -n increment] command
[argument]...
/usr/xpg4/bin/nice [-increment | -n increment] command
[argument]...
csh Builtin
nice [-increment | +increment] [command]
DESCRIPTION
The nice utility invokes command, requesting that it be run with a different system scheduling priority. The priocntl(1) command is a more
general interface to scheduler functions.
The invoking process (generally the user's shell) must be in a scheduling class that supports nice.
If the C shell (see csh(1)) is used, the full path of the command must be specified. Otherwise, the csh built-in version of nice will be
invoked. See csh Builtin below.
/usr/bin/nice
If nice executes commands with arguments, it uses the default shell /usr/bin/sh (see sh(1)).
/usr/xpg4/bin/nice
If nice executes commands with arguments, it uses /usr/xpg4/bin/sh (see ksh(1)).
csh Builtin
nice is also a csh built-in command with behavior different from the utility versions. See csh(1) for description.
OPTIONS
The following options are supported:
-increment | -n increment increment is a positive or negative decimal integer that has the same effect on the execution of the utility
as if the utility had called the nice() function with the numeric value of the increment option-argument. See
nice(2). nice() errors, other than EINVAL, are ignored. If not specified, an increment of 10 is assumed.
The super-user may run commands with priority higher than normal by using a negative increment such as -10. A
negative increment assigned by an unprivileged user is ignored.
OPERANDS
The following operands are supported:
command The name of a command that is to be invoked. If command names any of the special built-in utilities (see shell_builtins(1)),
the results are undefined.
argument Any string to be supplied as an argument when invoking command.
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of nice: LANG, LC_ALL, LC_CTYPE, LC_MES-
SAGES, PATH, and NLSPATH.
EXIT STATUS
If command is invoked, the exit status of nice will be the exit status of command. Otherwise, nice will exit with one of the following val-
ues:
1-125 An error occurred.
126 command was found but could not be invoked.
127 command could not be found.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
/usr/bin/nice
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
|CSI |Enabled |
+-----------------------------+-----------------------------+
/usr/xpg4/bin/nice
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWxcu4 |
+-----------------------------+-----------------------------+
|CSI |Enabled |
+-----------------------------+-----------------------------+
|Interface Stability |Standard |
+-----------------------------+-----------------------------+
SEE ALSO csh(1), ksh(1), nohup(1), priocntl(1), sh(1), shell_builtins(1), nice(2), attributes(5), environ(5), standards(5)SunOS 5.11 23 Jan 2004 nice(1)