Sponsored Content
Full Discussion: No utmpx entry.
Top Forums UNIX for Dummies Questions & Answers No utmpx entry. Post 1167 by 98_1LE on Monday 12th of February 2001 12:37:23 PM
Old 02-12-2001
FWIW, I solved this problem by killing utmpd, flushing the following files in /var/adm: utmp, utmpx, wtpm & wtmpx and restarting utmpd.
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

utmpx ???

:confused: HI... I am a brasilian software maker. I have a message " utmpx - filesystem isfull - /var/messages/unable to edit data " Like resolves its problem ??? Tank yours.... (2 Replies)
Discussion started by: jaimi.passos
2 Replies

2. UNIX for Advanced & Expert Users

shutting down 5.7 on Intel: failed to write of utmpx entry

When shutting down a freshly installed version of 5.7 on a Compaq server I get two messages: INIT: failed to write of utmpx entry: "s0" and: INIT: failed to write of utmpx entry: "fw" then I can continue with the shutdown. When I bring the system back up it has not saved any of my... (2 Replies)
Discussion started by: DarkLord
2 Replies

3. SCO

Failed Write of utmpx entry

I had a drive go bad. I have replaced the drive and have my system up. I have a 1-to-1 mirror raid. My mirrored boot drive brings the system up. I issued a reboot command. The system comes up gives me a login prompt and generates the error: failed write of utmpx entry:"i2". What is i2? (1 Reply)
Discussion started by: jwideman
1 Replies

4. AIX

crontab entry

Hi. I'm new to AIX and I need to create a crontab entry to run a script every first 5 business days of the month? please help. (2 Replies)
Discussion started by: udelalv
2 Replies

5. Red Hat

entry in /etc/hosts

Hello all, I´m on Red Hat Enterprise Server 4.5 I´m wondering if it is possible to disable the need to add every IP machine entry in the file /etc/hosts to allow it to connect to Red hat? I´m getting "where are you?" message. This is solved adding the machine ip where I´m working. Thanks in... (1 Reply)
Discussion started by: mig28mx
1 Replies

6. UNIX for Dummies Questions & Answers

cron entry

Can someone please quickly respond to this? I need to have a script test.sh to run every 30 minutes from Monday to Saturday from 6am to 10pm as a crontab entry... Thanks. (3 Replies)
Discussion started by: everurs789
3 Replies

7. UNIX for Dummies Questions & Answers

no utmpx entry and other questions

I have recently been assigned to help maintain some testing software on two UNIX stations. The stations are connected to instruments that supply power, signals, and take measurements from a box. Both test stations are basically the same. I was given a crash course (read a little training) a couple... (18 Replies)
Discussion started by: bjstaff
18 Replies

8. Shell Programming and Scripting

How to append an entry?

Hi i have following sample entry--Each entry has 7-9 lines. Below entry has 7 lines. I have a file it contains 1000's of such entries and each entry has 7-9 lines. Input: dn:cn=aci,cn=index,cn=example,cn=ldbm database, cn=plugins,cn=config objectClass: top objectClass:... (2 Replies)
Discussion started by: buzzme
2 Replies

9. How to Post in the The UNIX and Linux Forums

Help me, write a bash script to delete parent entry with all their child entry in LDAP UNIX server

Hi All, Please help me and guide me to write a bash/shell script on Linux box to delete parent entry with all their child entries. example: Parent is : ---------- dn: email=yogesh.kumar@wipro.com, o=wipro, o=in child is: ---------- dn: cn: yogesh kumar, email=yogesh.kumar@wipro.com,... (1 Reply)
Discussion started by: Chand
1 Replies

10. Shell Programming and Scripting

How to replace multiple "&nbsp;" entry with in <td> tag into single entry using sed?

I have the input file like this. Input file: 12.txt 1) There are one or more than one <tr> tags in same line. 2) Some tr tags may have one <td> or more tna one <td> tags within it. 3) Few <td> tags having "<td> &nbsp; </td>". Few having more than one "&nbsp;" entry in it. <tr> some td... (4 Replies)
Discussion started by: thomasraj87
4 Replies
hosts.equiv(4)						     Kernel Interfaces Manual						    hosts.equiv(4)

NAME
hosts.equiv - A file containing the names of remote systems and users that can execute commands on the local system SYNOPSIS
/etc/hosts.equiv DESCRIPTION
The /etc/hosts.equiv file and the .rhosts file in a user's home directory contain the names of remote hosts and users that are equivalent to the local host or user. An equivalent host or user is allowed to access a local nonsuperuser account with the rsh command or rcp com- mand, or to log in to such an account without having to supply a password. The /etc/hosts.equiv file specifies equivalence for an entire system, while a user's .rhosts file specifies equivalence between that user and remote users. The local user and the target system exist in the same area as the hosts.equiv file. The .rhosts file must be owned by the user in whose home directory the file is located, or by the superuser. It cannot be a symbolic link. Each line, or entry, in hosts.equiv or .rhosts may consist of the following: A blank line. A comment (begins with a #). A host name (a string of any printable characters except newline, #, or white space). In addition, an NIS netgroup can be specified in place of the host name. A host name followed by white space and a user name. In addition, an NIS netgroup can be specified in place of the host name, user name, or both. A single plus (+) character. This means any host and user. The keyword NO_PLUS. This keyword disallows the use of the plus character (+) to match any host or user on a system-wide basis. By default, the line containing this keyword is a comment. Remove the com- ment character to disallow the use of the plus character. Entries in the hosts.equiv file are either positive or negative. Positive entries allow access; negative entries deny access. The following entries are positive: host name user name +@netgroup In addition, the plus sign (+) can be used in place of the host name or user name. In place of the host name, it means any remote host. In place of the user name, it means any user. The following entries are negative: -host name -user name -@netgroup To be allowed access or denied access, a user's remote host name and user name must match an entry in hosts.equiv or .rhosts. The hosts.equiv file is searched first; if a match is found, the search ends. Therefore, the order in which the positive and negative entries appear is important. If a match is not found, .rhosts is searched if it exists in the user's home directory. A host name or user name can match an entry in hosts.equiv in one of the following ways: The official host name (not an alias) of the remote host matches a host name in hosts.equiv. The remote user name matches a user name in hosts.equiv. If a user name parameter is included in the hosts.equiv file, this means that the remote user is a trusted user and is allowed to rlogin to any local user account without being prompted for a password. Otherwise, if the user name parameter is not specified in the hosts.equiv file, the name of the remote user must match that of the local user. If the remote user name does not match a user name in hosts.equiv, the remote user name matches the local user name. CAUTIONS
For security purposes, the files /etc/hosts.equiv and .rhosts should exist and be readable and writable only by the owner, even if they are empty. EXAMPLES
The following are sample entries in an /etc/hosts.equiv file: # Allows access to users on host1 and host2 that have accounts on this host: host1 host2 # Allows access to user johnson on host1 to any local user: host1 johnson # Allows access to all users on systems specified in netgroup chicago +@chicago # Denies access to users specified in netgroup finance on host5 host5 -@finance # Allows access to all users on all systems except root + -root RELATED INFORMATION
Commands: rcp(1), rlogin(1), rsh(1) Functions: ruserok(3). Files: netgroup(4) Daemons: rlogind(8), rshd(8) delim off hosts.equiv(4)
All times are GMT -4. The time now is 11:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy