Re: [osol-discuss] How to debug a weird nis+ issue?
Hi Peter It is as followings passwd: compat files nis shadow: compat files nis group: files nis On Thu, Sep 18, 2008 at 9:36 AM, Yue Chen [EMAIL PROTECTED] wrote: Hi everyone I have a host installed with NIS+ client. There is a user named jsn in NIS server. His login shell is /bin/true. So he can not log on my host by default. Now I wanna grant his access so I added following line into /etc/passwd. +jsn::/bin/tcsh However, sometimes he is still unable to log on my host. To debug, I wrote a test binary using getpwnam to grab the user info and then check pw-pw_shell. To my surprise, the value for pw_shell is rather unstable. Sometimes it is /bin/tcsh (login is ok), sometimes it is /bin/true (login fails). How can I dig deeper on this weird issue? This issue almost drives me crazy. What does the passwd entry in your /etc/nsswitch.conf file look like? (Are you using compat?) -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] How to debug a weird nis+ issue?
Hi everyone I have a host installed with NIS+ client. There is a user named jsn in NIS server. His login shell is /bin/true. So he can not log on my host by default. Now I wanna grant his access so I added following line into /etc/passwd. +jsn::/bin/tcsh However, sometimes he is still unable to log on my host. To debug, I wrote a test binary using getpwnam to grab the user info and then check pw-pw_shell. To my surprise, the value for pw_shell is rather unstable. Sometimes it is /bin/tcsh (login is ok), sometimes it is /bin/true (login fails). How can I dig deeper on this weird issue? This issue almost drives me crazy. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] does the issue that writing more than 1K bytes to pty hangs still exist on Solaris8/10?
Hi Solaris experts I am new for Solaris development. But I have developed on Linux for several year. Recently I have to transform a program from Linux to Solaris. The program uses ssh to connect to a remote host and redirects the input/output of ssh to a unix socket locally. It also has a component to send commands into the unix socket. After the commands are transferred to remote host and executed there, the results are received from the same unix socket. This program works very well on linux. However, when remote host is solaris, if the command line is longer than 1024 bytes, sometimes some bytes can not reach the remote host. This phenomenon occurs mainly in case my program connects to the unix socket as soon as the ssh connection is created. If I make the program sleep several seconds after the connection is created. This issue rarely happens. I also made hundreds of stress tests for command line less than 1024 bytes. This issue absolutely can not be reproduced. I searched on Sun site and found that following bug is similar to my issue. === program hangs writing 1K bytes or more to pseudo terminal bug 1209258 http://sunsolve.sun.com/search/document.do?assetkey=1-1-1209258-1 - Jun 6, 1995 === But this bug is reported in 1995, rather ancient one. Does it still not fixed? I am so puzzled. Could anyone explain this to me? Thank you very much ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
