11-10-2002
License Issue....
Quote below from this site:
http://nscp.upenn.edu/aix4.3html/aix...ef/err3004.htm
Quote:
3004-312 All available login sessions are in use
Possible Causes:
You tried to log in to a system that had all present sessions in use.
Procedures for Recovery:
Change the number of license users in your system.
Log in to your system as the root user.
List the number of license users by running the lslicense command.
Increase the number of license users by running the chlicense command.
Restart your system in order for this change to take effect.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Help me please,
I wanna know if it's possible to define in windows the option when somebody starts a telnetsession to a unix machine it automatically logs in with the username and password of this user. Or if there is a possibility to set the username and password to an Icon on the users... (3 Replies)
Discussion started by: Herwin
3 Replies
2. UNIX for Advanced & Expert Users
Hi All,
I've login to Unix using login name guest and I'm working on it,
I need another session to run some script hence tried to login
but password invalid it says here my question is :
Since I'm in working in one session can I set the password without knowing old password? is there any... (1 Reply)
Discussion started by: krishna
1 Replies
3. UNIX for Dummies Questions & Answers
Im having a problem using unix program client ReflectionX. as soon as i login to one session i type to change to any directory or type something but the problem is that what i type in is not what you get. ie i type:
$cd ~/alejo (to change HOME DIRECTORY - alejo subdirectory
but when i type it... (2 Replies)
Discussion started by: alexcol
2 Replies
4. Shell Programming and Scripting
Hi,
I'm currently working on a perl website, and I would need a system where a few users can login into the administration side of the site. about 5-10 users maximum, all pretty simple.
I was thinking of using an .htaccess file and a seperate admin folder on the server. I'm wondering if there... (2 Replies)
Discussion started by: LNC
2 Replies
5. Solaris
I am not able to login in gnome session and java session in Sun solaris 9& 10 respectively through xmanager as a nis user, I am able to login in common desktop , but gnome session its not allowing , when I have given login credentials, its coming back to login screen, what shoul I do to allow nis... (0 Replies)
Discussion started by: durgaprasadr13
0 Replies
6. HP-UX
Hi,
I am a hobbyist with a very old machine I have been trying to get up and running. I have an HP 9000/C240 with 1G of RAM and 3-8.5G HD. It is configured with 1G SWAP/DUMP. Currently only one drive is in use via LVM. I have not gotten around to creating more volumes just yet.
It is running... (11 Replies)
Discussion started by: Dirk_
11 Replies
7. Shell Programming and Scripting
How to record my login session in a file named session.lst? (1 Reply)
Discussion started by: anupdas
1 Replies
8. Shell Programming and Scripting
Besides 'who am i' and 'tty' what commands could be used to determine if a session is interactive as compared to a web process or cron process. Any command should work with the common unix variants. (3 Replies)
Discussion started by: jgt
3 Replies
9. Shell Programming and Scripting
Hi
I need to track what commands run in login session in solaris whether it is root or any normal users in bash shell.
My actual requirement is that when a user (nomal/root) login into the system, whatever commands he run, it should log into file on specified path . I don't require command... (4 Replies)
Discussion started by: hb00
4 Replies
10. UNIX for Advanced & Expert Users
Hi,
How can I find out the login and logout time of the old UNIX session/user?. (2 Replies)
Discussion started by: sharif
2 Replies
LEARN ABOUT ULTRIX
shutdown
shutdown(8) System Manager's Manual shutdown(8)
Name
shutdown - close down the system at a given time
Syntax
/etc/shutdown [ -k ] [ -r ] [ -h ] [ -o ] time [ warning-message ... ]
Description
The command provides an automated shutdown procedure that a superuser can use to notify users when the system is shutting down.
The time is the time at which will bring the system down. It may be the word `now', indicating an immediate shutdown, or specify a future
time in one of two formats: + number or hour : min. The first form brings the system down in number minutes. The second brings the system
down at the time of day indicated, using a 24-hour clock format.
At intervals which get shorter as shutdown nears, warning messages are displayed at the terminals of all users on the system. Warning mes-
sages are also sent to users who are logged in to a remote system that has mounted a file system or directory from the local system using
NFS. Five minutes before shutdown, or immediately if shutdown is timed for less than five minutes, logins are disabled by creating and
writing a message there. If this file exists when a user attempts to log in, prints its contents and exits. The file is removed just
before exits.
At shutdown time, a message is written in the file This message contains the time of shutdown, who ran shutdown, and the reason. Then, a
terminate signal is sent at to bring the system to single-user state.
If the or options are used, then executes or avoids shutting the system down (respectively). The option is for use by only. It indicates
to that it is being called by and not to return to the user.
You should place the time of the shutdown and the warning message in Use the message to inform the users about when the system will be back
up and why it is going down.
Restrictions
You can kill the system only between now and 23:59, if you use the absolute time for shutdown.
Files
Tells login not to let anyone log in
Log file for successful shutdowns
See Also
login(1), wall(1), halt(8), opser(8), reboot(8), rwalld(8c)
shutdown(8)