Sponsored Content
Full Discussion: root login problem in cde
Operating Systems HP-UX root login problem in cde Post 79934 by zazzybob on Tuesday 2nd of August 2005 08:10:22 AM
Old 08-02-2005
awadhesh,

Please post your question in an appropriate forum. I have moved this thread.

Thanks,
ZB
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Root Login Problem

I have Sun Netra X1 Server which is headless means no CDROM, no terminal etc. I am connected it through serial port. Accidently, someone in our department changed the root's default shell to /sbin/tcsh while there is no tcsh in /sbin and he logs off. Now, I am trying to logon as root on system... (2 Replies)
Discussion started by: s_aamir
2 Replies

2. HP-UX

CDE login Problem for root user only

Hi All, I m facing a problem that, i m not able to login as root user on cde on hp-ux 11.00, i can login as root on commond line as well as telnet. Thanks in Advance for help. Regards, Awadhesh (1 Reply)
Discussion started by: Awadhesh
1 Replies

3. UNIX for Advanced & Expert Users

CDE Login Banner

I'm having problem with the CDE pre login banner. I configured the c/usr/dt/config/C/Xresources file to add my warning message: Dtlogin*greeting.labelString: My Banner I then modified the Dtlogin*greeting*fontList to display the message in smaller text. This did not work. ... (1 Reply)
Discussion started by: equismorio
1 Replies

4. Solaris

Not able to login through JDS but able to login through CDE

Dear All I am in a strange situation where I have install the Solaris 10 5/08 OS on Netra 1280 server. When I connect it through my laptop so that I can take the GUI from xmanager. When I try to login as root or any other users also through Java Destop Environment which accepted it after few... (3 Replies)
Discussion started by: girish.batra
3 Replies

5. HP-UX

Help with CDE Root Login

Dear Forum, I had this problem initially with HPUX 11.23, all users including root could not login via CDE or telnet. Then after some workarounds, it resolved by resetting root password via console login. After enabling back all users to login normally (via CDE or telnet), only root can not... (4 Replies)
Discussion started by: irda
4 Replies

6. AIX

Can't login on CDE AIX 4.2

Hi, can somebody please, please help me? After a power loss and server restart my server running AIX 4.2.2 could not boot. Following the procedure in my user guide I checked the hd's with # fsck -y /dev/hd1 # fsck -y /dev/hd2 # fsck -y /dev/hd3 # fsck -y /dev/hd4 # fsck -y /dev/hd9var I... (0 Replies)
Discussion started by: semso
0 Replies

7. UNIX for Dummies Questions & Answers

Can't login on CDE AIX 4.2

Hi, can somebody please, please help me? After a power loss and server restart my server running AIX 4.2.2 could not boot. Following the procedure in my user guide I checked the hd's with # fsck -y /dev/hd1 # fsck -y /dev/hd2 # fsck -y /dev/hd3 # fsck -y /dev/hd4 # fsck -y /dev/hd9var ... (4 Replies)
Discussion started by: semso
4 Replies

8. UNIX for Advanced & Expert Users

Unix user with root power problem in to login in putty

Hello, I created a user in my AIX 5.3 system and i modified /etc/passwd file in and assigned this user the uid=0 like root user. The problem is that when this user log into the system through putty it asks for root password instead of the user password. As a result of this, if i reset the... (4 Replies)
Discussion started by: omonoiatis9
4 Replies

9. Solaris

Problem with root login

Hi, we have instaled Solaris 10 on a SUN V490, installation went okay but now when I type “root” and press return it comes back with the “Login incorrect” without ever asking for a password... (6 Replies)
Discussion started by: manni2
6 Replies
postwait(2)							System Calls Manual						       postwait(2)

NAME
postwait: pw_getukid(), pw_wait(), pw_post(), pw_postv(), pw_getvmax() - lightweight synchronization mechanism SYNOPSIS
DESCRIPTION
Postwait is a fast, lightweight sleep/wakeup mechanism that can be used for synchronization by cooperating kernel threads within a single process or between separate processes. A thread calls to block. It resumes execution when it is posted by another thread, the call expires, or is signaled. If one or more posts are already pending, returns immediately. Threads using postwait are identified by their ukid. A thread retrieves its ukid by calling It shares this ukid with anyone it chooses by any means it considers appropriate (for example, shared memory). is called with a timeout ts. If ts is NULL, the thread will not timeout. It will remain blocked until posted or a signal wakes it up. If ts points to a zero-valued timespec, will return immediately with a value (and indicating whether or not it was posted. If ts points to a timespec whose value is greater than zero, the thread will block for that amount of time unless it is posted or inter- rupted by a signal, in which case the timespec pointed to by ts is updated with the remaining time. The return value and are set to indi- cate the reason the call returned. is used to post many threads with a single call. It posts to all threads in the targets array. An value for each target is returned in the errors array. (0 indicates success.) If the errors pointer is zero, no target-specific errors are copied out. There is a maximum number of threads that can be posted with a single call. This value is returned by Posts sent to a kernel thread that already has a post pending against it are discarded. RETURN VALUE
returns 0 if it succeeds, -1 otherwise. returns 0 if posted, -1 otherwise. returns 0 if the post succeeds, -1 otherwise. returns 0 if every post succeeds, -1 otherwise. returns the maximum number of kernel threads that can be posted with a single call to ERRORS
sets to one of the following values if it fails: ukid points to an illegal address. The reliable detection of this error is implementation dependent. sets to one of the following values if it fails: was called with a timeout of 0 but the caller has no post(s) pending. was called with a timeout that expired. ts points to an illegal address. The reliable detection of this error is implementation dependent. was interrupted by a signal. The timespec pointed to by ts is invalid. sets to one of the following values if it fails: The ukid refers to a non-existent kernel thread. sets to one of the following values if it fails: targets points to an illegal address. The reliable detection of this error is implementation dependent. errors points to an illegal address. The reliable detection of this error is implementation dependent. count is less than 0. count exceeds the maximum value (as returned by A ukid refers to a non-existent kernel thread. postwait(2)
All times are GMT -4. The time now is 10:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy