This is a discussion on Solaris: x-client login in very slow. within the Sun Solaris Administration forums, part of the Solaris Operating System category; --> Hi, I am having this strange situation, we are using Humming bird exceed as X tool to login to ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi, I am having this strange situation, we are using Humming bird exceed as X tool to login to Solaris from windows. Somehow, when users try to login, after type in password, it just hang there, no error msg, and no logged terminal as well. when if I go to dos mode, and do "telnet", it comes up right away. when I do "df", I notify that the space under root partion "/" is getting less and less, while I can't find anything using "/", except "/ proc". After certain login time, I didn't do anything, I got space back from "/", and system login fine, I check /var/adm/messages, there is only one error for windows nfs mapping (we use CPIO to backup to window nfs mapping and that mount point is under "/", but there is no CPIO pid found) What could be wrong to prevent x-login? |
| ||||
| On Jun 17, 7:42 pm, steeles <stee...@gmail.com> wrote: > Hi, > > I am having this strange situation, we are using Humming bird exceed > as X tool to login to Solaris from windows. Somehow, when users try to > login, after type in password, it just hang there, no error msg, and > no logged terminal as well. > > when if I go to dos mode, and do "telnet", it comes up right away. > > when I do "df", I notify that the space under root partion "/" is > getting less and less, while I can't find anything using "/", except "/ > proc". > > After certain login time, I didn't do anything, I got space back from > "/", and system login fine, I check /var/adm/messages, there is only > one error for windows nfs mapping (we use CPIO to backup to window nfs > mapping and that mount point is under "/", but there is no CPIO pid > found) > > What could be wrong to prevent x-login? Many possible reasons: This could be due to your X initiliazing files in yor home directoy, as you have mentioned in your OP, you might have some dependacies on the NFS mounted filesytems when starting X console. try using /starting Xsun with debug mode enabled, this will give you some clue what is there... ... It's suggested to not to place the /var system under root, when you have a extensive log producing applications running on the system, otherwise you may endup with the root space on ( did you 'tunefs -m 1' ?) try looking at the things which relate to the initialization of X session, ( did you try with Xmanager, does the result remain same?) Regards, Moody Motorola Pk. |