Bob,

I'm trying to think back through all of the steps I took, so this is from memory and may not be entirely accurate.

I did a fresh install of SuSE Enterprise 10 SP2, with all of the recommended packages. I then installed SRSS 4.1. utinstall worked perfectly, with no errors of any kind. After this, I ran utadm -l eth1 to setup the DHCP on the private network. I then ran utconfig.

At this point, I was getting 26D errors on the DTU. I tried numerous things to get this to work, including modifying the custom.conf file according to some random information I found on google searches. This is most likely when I added these lines in.

At some point, I was getting GDM to load on the DTU and immediately greeted with an error message with something to the effect that GDM could not load correctly. At this point I strace'd the GDM process and found out that GDM couldn't access /usr/libexec because the directory permissions were set to 700. I changed it to 755 and things started working, except of course for the no user issue.

I'm doing all of this on a test machine as a proof-of-concept and will be doing this all over again in the near future. I will try to keep better records of the steps I take and post them afterwords.

I'll try removing those lines and/or running utctl when I get back to the office on Monday and let you know what happens.

Let me know if there's anything else you would like to know or would like me to try.

Thanks again,
-Kevin


On Nov 21, 2008, at 7:40 PM, Bob Doolittle wrote:

I'm glad you're running, but this shouldn't be necessary. We'd like to understand what went wrong. Those lines should not exist in your custom.conf. If you look in the standard directories (e.g. /etc/X11/ gdm/PostLogin) you should see symlinks to the files in /etc/opt/ SUNWut/gdm/SunRayPostLogin. Do you?

If you run "/opt/SUNWut/lib/utctl disable; /opt/SUNWut/lib/utctl enable" do those lines go away?

If not, try removing those lines manually, and restarting your system. That should resolve your issue.

Was this system upgraded from a previous release? What release? Maybe we have an upgrade bug and used to use those lines but neglected to strip them out in the disable phase... How did you perform your upgrade? Did it appear to complete successfully or did you get any unusual messages or errors?

Does this custom.conf file have any unusual history? Was it copied onto the system after utinstall, for example?

We'd appreciate your assistance in root-causing this issue, so that if there's a bug we can fix it for other users also.

Thanks,
 Bob

Kevin Farrell wrote:
Solved!
Jörg: Thanks for the help!

I changed gdm's custom.conf file from:
PostLoginScriptDir=/etc/X11/gdm/SunRayPostLogin/
PreSessionScriptDir=/etc/X11/gdm/SunRayPreSession/
PostSessionScriptDir=/etc/X11/gdm/SunRayPostSession/
DisplayInitDir=/etc/X11/gdm/SunRayInit
to:
PostLoginScriptDir=/etc/opt/SUNWut/gdm/SunRayPostLogin/
PreSessionScriptDir=/etc/opt/SUNWut/gdm/SunRayPreSession/
PostSessionScriptDir=/etc/opt/SUNWut/gdm/SunRayPostSession/
DisplayInitDir=/etc/opt/SUNWut/gdm/SunRayInit

and that took care of it.

Thanks!
-Kevin
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users


_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users


_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to