Sponsored Content
Full Discussion: Error login user file utmp
Top Forums UNIX for Dummies Questions & Answers Error login user file utmp Post 27737 by jernesto_diaz on Thursday 5th of September 2002 05:59:47 PM
Old 09-05-2002
Error login user file utmp

could probably help me with a unix problem.
Basicallyu, when the users try to connect to the server they get this messge:
No UTMP entry. you must exec "LOGIN" from the lowest level "sh"

They are connecting using a windows emulator called TINYTERM.

We cannot connect from the console either (not even with root)....only in single user mode.

Any Ideas?
 

10 More Discussions You Might Find Interesting

1. SCO

SCO utmp file

I am tring to recover a SCO system remotely, when I try to login with multiple user support, i get the following message No UTPM entry, you must execute from the lowest level (sh) Can anyone shed some light on this issue. I have never came seen this error before. Also it will allow me to... (1 Reply)
Discussion started by: scott_williams1
1 Replies

2. HP-UX

Hp-Unix user login file collection

Dear All, how to check the unix log file which mean how many(who) user has been log in the server for the day, when they log in & when they log out? (8 Replies)
Discussion started by: whl123
8 Replies

3. UNIX for Dummies Questions & Answers

I create user but i cant login the user i created.

I created a user, i login as a root. I add him in the group where he can access and login as a root! I checked it in users' list and in group's list, he is there. My problem is this, I cant login using the username/account I just created! What should i do to use and login the user/account i've just... (5 Replies)
Discussion started by: jerome
5 Replies

4. UNIX for Dummies Questions & Answers

Error, Login Limit Exceeded by 1 user

Would appreciate some help, system was displaying an error regarding the kernal when a "sar" was run, after a reboot we get "WARNING user login limit exceeded by 1 user". We have plenty of licences. any ideas? (1 Reply)
Discussion started by: nchrocc
1 Replies

5. UNIX for Advanced & Expert Users

/etc/utmp file does not get updated with boot up details

In a frequent interval the system bootup is not updating the /etc/utmp file with the system boot details. This leads to blank output of who - b command. What can be the reason for the same? (1 Reply)
Discussion started by: jyoti_mil
1 Replies

6. UNIX for Dummies Questions & Answers

Help Needed using utmp file!

Hi. I am working on a small assignment where i need to extract the login information of currently logged in users in a Linux client-server environment.I am able to extract only the userID,IP/HOST name,TTY,device name,GID,PID and login time using the structure 'utmp'.Also when i am saving the... (2 Replies)
Discussion started by: maverixxx
2 Replies

7. 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... (1 Reply)
Discussion started by: lifegeek
1 Replies

8. Shell Programming and Scripting

error in .login file

I have one server (consider A) .While logining into server A using username as u1 .I am not getting any command not found error but while I am loging into that server A using username as u2 , I am getting this below error while login... (5 Replies)
Discussion started by: maitree
5 Replies

9. Shell Programming and Scripting

How to Login as another user through Shell script from current user[Not Root]

Hi Every body, I would need a shell script program to login as different user and perform some copy commands in the script. example: Supppose ora_toms is the active user ora_toms should be able to run a script where user: ftptomsp pass: XXX should login through and run the commands ... (9 Replies)
Discussion started by: ujjwal27
9 Replies

10. AIX

User Account Login Login on your AIX server

I want to learn AIX. I would like to find someone who would be willing to give me a login to their AIX home lab server. My intent is to poke around and discover the similarities and differences of AIX compared to other *NIXs. I am a UNIX admin so I can think of what some immediate concerns may... (1 Reply)
Discussion started by: perl_in_my_shel
1 Replies
BOOT(8) 						      System Manager's Manual							   BOOT(8)

NAME
boot - connect to the root file server SYNOPSIS
/boot [ -fkm ] [ -uusername ] [ method!fs-addr ] DESCRIPTION
Boot is the first program run after a kernel has been loaded. It connects to the file server that will serve the root, performs any authentication needed to connect to that server, and exec(2)'s the init(8) program. It is started by the kernel, never run directly by the user. See booting(8) for information about the process of loading the kernel (and boot) into memory. Once loaded, the kernel initializes its data structures and devices. It sets the two environment variables /env/cputype and /env/terminal to describe the processor. It then binds a place-holder file server, root(3), onto / and crafts an initial process whose sole function is to exec(2) /boot, a binary which is compiled into root(3). The command line passed depends on the information passed from boot ROM to kernel. On the MIPS Magnum and SGI Power Series the command line passed to boot is the same as that given to the ROM monitor. On AT&T Gnots the command line is /68020/9gnot method!server On the Nextstation , no information is passed from the boot ROM or program. The command line is /68020/9nextstation On the PC, each line in the DOS file plan9.ini of the form name=value is passed to the boot program as an environment variable with the same name and value. The command line is /386/9pc method!server Boot must determine the file server to use and a method with which to connect to it. It must also set a user name to be used as the owner of devices and all console processes and an encryption key to be used when challenged. Boot will prompt for these. Method and address are prompted for first. The prompt lists all valid methods, with the default in brackets. root is from (il, tcp, hs, local)[il]: A newline picks the default. Other possible responses are method or method!address. To aid in automatic reboot, the default is automati- cally taken on CPU servers if nothing is typed within 15 seconds. The other interactions depend on whether the system is a terminal or a CPU server. Terminal The terminal must have a username to set. If none is specified with the -u option, boot will prompt for one on the console: user: The user will also be prompted for a password to be used as an encryption key on each attach(5): password: With most methods boot can now connect to the file server. However, with the serial line methods 9600 and 19200, the actual mechanics of setting up the complete connection are too varied to put into the boot program. Instead boot lets the user set up the connection. It prints a prompt on the console and then simulates a dumb terminal between the user and the serial line: Connect to file system now, type ctrl-d when done. (Use the view or down arrow key to send a break) The user can now type at a modem or a Datakit destination please: interface to set up the connection to a TSM8 card. At Murray Hill, a user would type nj/astro/plan85 at this point. When the user types a control-D, boot stops simulating a terminal and starts the file sys- tem protocol over the serial line. Once connected, boot mounts the root file system before / and makes the connection available as #s/boot for subsequent processes to mount (see bind(2)). Boot completes by exec(2)'ing /$objtype/init -t. If the -m option is given it is also passed as an option to init. If the kernel has been built with the cache file system, cfs(4), the local disk partition /dev/[sh]d[01]cache exists, and the root file system is from a remote server, then the kernel will insert a user level cache process between the remote server and the local namespace that caches all remote accesses on the local partition. The -f flag commands cfs to reformat the cache partition. CPU Servers The user owning devices and console processes on CPU servers and that user's domain and encryption key are read from NVRAM on all machines except PC's. PC's keep the information in the disk partition /dev/[sh]d[01]nvram. If a -k option is given or if no stored information is found boot will prompt for all three items and store them. password: authid: bootes authdom: research.att.com The key is used for mutual authentication of the server and its clients. The domain and id identify the owner of the key. Once connected, boot behaves as on the terminal except for exec(2)'ing /$objtype/init -c. Booting Methods The methods available to any system depend on what was compiled into the kernel. The complete list of booting methods are listed below. cyc connect via a point-to-point fiber link using Cyclone boards. If specified, the address must be the number of the Cyclone board to be used, default 0. il connect via Ethernet using the IL protocol. tcp connect via Ethernet using the TCP protocol. This method is used only if the initial file server is on a Unix system. hs connect via Datakit using the high speed Datakit card. incon connect via Datakit using the Incon interface. 9600 connect via Datakit using the serial interface at 9600 baud. 19200 connect via Datakit using the serial interface at 19200 baud. local connect to the local file system. For the il and tcp methods, the address must be a numeric IP address. If no address is specified, a file server address will be found from another system on the network using the BOOTP protocol and the Plan 9 vendor-specific fields. For the Datakit methods, hs, 9600, 19200, and incon, the address must be specified and must be a relative path name to the file server. If no address is specified, the address Nfs is used. FILES
#s/boot SOURCE
/sys/src/9/boot SEE ALSO
root(3), bootp(8), init(8) BOOT(8)
All times are GMT -4. The time now is 07:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy