Login Error 3004-304

7 More Discussions You Might Find Interesting

1. AIX

3004-312 All available login sessions are in use.

Hello, I have a strange situation here. I am running an AIX6.1 machine and i face a problem when i am trying to login via telnet. When i use my username and password to login to the server i get the following message: 3004-312 All available login sessions are in use. The weird thing is that...

2. AIX

Users can not login with telnet 3004-031

when all the users try to login using telnet they will counter the error 3004-031 . and they can not access the system . our application is sbglobus (temenos )

3. Solaris

error message rmclomv ... SC Login Failure for user Please login:

Hello World ~ HW : SUN Fire V240 OS : Solaris 8 Error message prompts 'rmclomv ... SC login failure ...' on terminal. and Error Message prompts continually 'SC Login Failure for user Please login:' on Single Mode(init S) The System is in normal operation, though In case of rain, Can...

4. AIX

Login Error 3004-304 aix 4.3 please help

hello, I am trying to log on and get an error "3004-304 You are not allowed to login at this time.". The server is in production level, works as a cluster under hacmp, the other server took the services but I cannot log into the first one. Please help me because I need to solve the problem as...

5. AIX

3004-505 Cannot set process environment

Guys I have an AIX 5.3 box.I am getting following messages if i try to switch to any non root user. bash-3.00# su - sys 3004-505 Cannot set process environment. bash-3.00# su - daemon 3004-505 Cannot set process environment. bash-3.00# su - adm 3004-505 Cannot set process environment....

6. UNIX for Advanced & Expert Users

VSI-FAX error - Cannot login to server and Connecto error to host

I encounters a VSIFAX related error: vfxstat: Cannot login to server on rsac3: Connect error to host 172.16.1.45: Invalid argument It started happening last night with a core dump. Then we can't start VSIFAX again. I am runing VSI-FAX 4.2 on AIX box

7. UNIX for Advanced & Expert Users

RDUBLK: cANNOT FİND PROCESS id ....

Hi, we are using SCO Open Server 5.0.7 on HP ProLiant DL380 G4 Intel(R) Xeon(TM) CPU 2.8 dual processor. 2 GB MEM. The error message is : ps: RDUBLK: Cannot find process ID ....: No such device or address (error 6) Best regards, Abdullah Sekman

LEARN ABOUT MOJAVE

getlogin

GETLOGIN(2)						      BSD System Calls Manual						       GETLOGIN(2)

NAME

     getlogin, setlogin -- get/set login name

SYNOPSIS

     #include <unistd.h>

     char *
     getlogin(void);

     int
     setlogin(const char *name);

DESCRIPTION

     The getlogin() routine returns the login name of the user associated with the current session, as previously set by setlogin().  The name is
     normally associated with a login shell at the time a session is created, and is inherited by all processes descended from the login shell.
     (This is true even if some of those processes assume another user ID, for example when su(1) is used.)

     setlogin() sets the login name of the user associated with the current session to name.  This call is restricted to the super-user, and is
     normally used only when a new session is being created on behalf of the named user (for example, at login time, or when a remote shell is
     invoked).

RETURN VALUES

     If a call to getlogin() succeeds, it returns a pointer to a null-terminated string in a static buffer.  If the name has not been set, it
     returns NULL.  If a call to setlogin() succeeds, a value of 0 is returned.  If setlogin() fails, a value of -1 is returned and an error code
     is placed in the global location errno.

ERRORS

     The following errors may be returned by these calls:

     [EFAULT]		The name parameter gave an invalid address.

     [EINVAL]		The name parameter pointed to a string that was too long.  Login names are limited to MAXLOGNAME (from <sys/param.h>)
			characters, currently 12.

     [EPERM]		The caller tried to set the login name and was not the super-user.

SEE ALSO

     setsid(2)

BUGS

     Login names are limited in length by setlogin().  However, lower limits are placed on login names elsewhere in the system (UT_NAMESIZE in
     <utmp.h>).

     In earlier versions of the system, getlogin() failed unless the process was associated with a login terminal.  The current implementation
     (using setlogin()) allows getlogin to succeed even when the process has no controlling terminal.  In earlier versions of the system, the
     value returned by getlogin() could not be trusted without checking the user ID.  Portable programs should probably still make this check.

HISTORY

     The getlogin() function first appeared in 4.4BSD.

4.2 Berkeley Distribution					   June 9, 1993 					 4.2 Berkeley Distribution

AIX