One of my Solaris machines is giving me this message whenever I try to open a second login session:

User XYZ has already been assigned a shell

Is there a file that sets a limit on the number of simultaneous login sessions you can have? I'm guessing so, but don't have enough experience with Solaris to know which file(s) to check.

Any advice would be appreciated.

Thanks!

Moved: This thread is more suitable in Solaris and has been moved accordingly to help your thread/question get the exposure it deserves.

Thanks! I hadn't realized there was a dedicated Solaris board. Woohoo!!!

Can you clarify this statement? Just how are you trying to start a second login session?

I beleive that you can start additional sessions (command-line mode) in a manner similar to Linux: ctrl+alt+F1 through ctrl+alt+F6 opens a virtual terminal to login to. ctrl+alt+F7 brings you back to your GUI session (in Linux). Some reading I've done says it's possible to setup ctrl+alt+F8 through ctrl+alt+F12 for additional GUI sessions, but I haven't succeeded in getting that working yet.

There may be something similar in Solaris using ctrl+alt+F? or perhaps alt+F? (where ? is the number of the function key).

There are tons of documentation here:
http://sunsolve.sun.com/show.do?target=home
http://www.sun.com/software/solaris/..._resources.jsp
http://solaris-x86.org/

You might find this expecially interesting: http://docs.sun.com/app/docs/doc/819...oq?l=en&a=view
Scroll down to this: Configuration of Session Quota Constraints

That wasn't too clear, was it? Sorry about that...

I telnet (or ssh) to the server and log into my regular terminal window. On all of my other UNIX/Linux servers, I can telnet/ssh in as many times as I want. On this one, it lets me log in normally the first time, but gives me the message "SORRY: [my user ID] has already been assigned a shell" if I try to connect a second time.

Several years ago, we had a security requirement that each user could only have one open connection at a time to any server. That requirement has since been eliminated and isn't present on any other servers, but I'm operating on the assumption that this server may still have that limit set. I just don't know where that setting is. (It's been sitting idle for some time, but is being put back into service.)

Thanks again!

This isn't a standard Solaris setting.

On place to search would be a custom account management pam module added in /etc/pam.conf