Hello All.
I have an E3500 running solaris 10 that I'd like to setup to
automatically start an Xsession as an unpriviledged user.  Following
Alan Coopersmith's reply [0] in a previous thread did exactly what I
needed on a blade 2000 (also running S10), however the same edit to the
dtlogin script on the E3500 resulted in an error message [1].  I looked
for the error message and found some info about installing the SUNWdfb
and SUNWdfbh packages.  I have only been able to track down the
SUNWdfbh package so far and on my way over to the server room to insert
another CD.   So far though, firing up dtlogin isn't getting the same
results as the Blade 2000.  Any thoughts?  I can get an Xsession
running on the E3500 via remote dtlogin over the network (as the
autologin user) so I know X is working at least to that point.  Oh, the
whole reason for this is so an Oracle reporting application (I think
it's called runwr60) has an X display to use so it can run.  I'm very
new to Oracle and it's utilities, so If anyone knows of a way to give
that thing an X display without all this monkeying around, that would
be appreciated as well.

Thanks!


[0]
http://groups.google.com/group/comp.unix.solaris/browse_thread/thread/add5b31814cc2d3b
[1]
chown: /dev/fb: No such file or directory

/dev/fb: No such file or directory
/dev/fb: No such file or directory
Graphics Adapter device /dev/fb is of unknown type

Fatal server error:
InitOutput: Error loading module for /dev/fb

giving up.
/usr/openwin/bin/xinit:  Network is unreachable (errno 128):  unable to
connect to X server
/usr/openwin/bin/xinit:  No such process (errno 3):  Server error.

In <1168440670.367235.292660@i56g2000hsf.googlegroups.com> "bl8n8r" <bl8n8r@yahoo.com> writes:

>I have an E3500 running solaris 10 that I'd like to setup to
>automatically start an Xsession as an unpriviledged user.  Following
>Alan Coopersmith's reply [0] in a previous thread did exactly what I
>needed on a blade 2000 (also running S10), however the same edit to the
>dtlogin script on the E3500 resulted in an error message [1].

With Solaris 10, this is easier and simpler to do under gdm than under
dtlogin.  See http://mail.cc.umanitoba.ca/dtautologin/ for one way to
configure this.


-- 
-Gary Mills-    -Unix Support-    -U of M Academic Computing and Networking-

Gary Mills wrote:
<snip>
> With Solaris 10, this is easier and simpler to do under gdm than under
> dtlogin.  See http://mail.cc.umanitoba.ca/dtautologin/ for one way to
> configure this.

I started setting this up until I got to the part:

    "The file /usr/lib/security/pam_allow.so.1 is not currently
included
     with Solaris 10. It can be     copied from one of the Nevada
     releases, for the appropriate platform, and installed in
     /usr/lib/security."

I did a search on opensolaris for this pam module [0], but couldn't
find a place to download it.  Is it a stand-alone tarball, or do I need
to dig it out of one of the alternate downloads [1] ?

Thanks


[0] - http://opensolaris.org/os/community/arc/caselog/2005/453/
[1] - http://opensolaris.org/os/downloads/

In <1168454065.954093.268870@p59g2000hsd.googlegroups.com> "bl8n8r" <bl8n8r@yahoo.com> writes:

>Gary Mills wrote:
><snip>
>> With Solaris 10, this is easier and simpler to do under gdm than under
>> dtlogin.  See http://mail.cc.umanitoba.ca/dtautologin/ for one way to
>> configure this.

>I started setting this up until I got to the part:

>    "The file /usr/lib/security/pam_allow.so.1 is not currently
>included
>     with Solaris 10. It can be     copied from one of the Nevada
>     releases, for the appropriate platform, and installed in
>     /usr/lib/security."

>I did a search on opensolaris for this pam module [0], but couldn't
>find a place to download it.  Is it a stand-alone tarball, or do I need
>to dig it out of one of the alternate downloads [1] ?

I just checked Solaris 10 11/06.  That release still doesn't have the
pam_allow.so.1 file.  You may have to download the entire installation
image for a recent Nevada release to get a copy of the file.  It's in
the SUNWcsl package.


-- 
-Gary Mills-    -Unix Support-    -U of M Academic Computing and Networking-

Gary Mills wrote:
<snip>
> I just checked Solaris 10 11/06.  That release still doesn't have the
> pam_allow.so.1 file.  You may have to download the entire installation
> image for a recent Nevada release to get a copy of the file.  It's in
> the SUNWcsl package.
>
>
> --
> -Gary Mills-    -Unix Support-    -U of M Academic Computing and Networking-

Thanks for the info.  I'll go grab some iso and see if I can find the
package.
Links are here if anyone is interested.

http://www.opensolaris.org/os/downloads/sol_ex_dvd/
http://www.opensolaris.org/os/downloads/sol_ex_cd/

PS:
Just in case anyone can use it, I adapted an inittab entry from Knoppix
to work for logging in a user with a bash shell.  Commands to run can
be stuck in the someuser .bashrc file.  Starting an Xsession from
..bashrc didn't work for me though.  Maybe /dev perms..

(watch for line breaks..)

a3:234:respawn:/bin/su someuser -c /bin/bash -login >/dev/console 2>&1
</dev/console

Gary Mills wrote:
> In <1168454065.954093.268870@p59g2000hsd.googlegroups.com> "bl8n8r" <bl8n8r@yahoo.com> writes:
>
> >Gary Mills wrote:
> ><snip>
> >> With Solaris 10, this is easier and simpler to do under gdm than under
> >> dtlogin.  See http://mail.cc.umanitoba.ca/dtautologin/ for one way to
<snip>


I've installed installed the SUNWcsl* packages to /tmp/ and then just
copied pam_allow, and the symlink, to /usr/lib/security. Should the
entire Nevada:SUNWcsl* packages be installed, or will this cause some
inconsistencies with the rest of the system?

Issuing "/usr/local/sbin/dtautologin start"  seems to just loop [0]
over starting the Xserver.  Any ideas why this is?   I'll go over the
install in case I've goofed.

Thanks



[0]
[root@oas /var/dt]# tail -f Xerrors
/dev/fb: No such file or directory
/dev/fb: No such file or directory
Graphics Adapter device /dev/fb is of unknown type

Fatal server error:
InitOutput: Error loading module for /dev/fb

Couldn't open display connection :0
/usr/openwin/bin/xrdb: Network is unreachable
/usr/openwin/bin/xrdb: Can't open display ':0'
xsetroot:  unable to open display ':0'
/usr/openwin/bin/xset:  unable to open display ":0"
/usr/openwin/bin/xmodmap:  unable to open display ':0'
usage:
        chown [-fhR] owner[:group] file...
        chown -R [-f] [-H|-L|-P] owner[:group] file...
su: Unknown id: start
/usr/local/sbin/dtautologin: kill: no such process
/dev/fb: No such file or directory
/dev/fb: No such file or directory
Graphics Adapter device /dev/fb is of unknown type

Fatal server error:
InitOutput: Error loading module for /dev/fb

In <1168615439.503571.69700@v45g2000cwv.googlegroups.com> "bl8n8r" <bl8n8r@yahoo.com> writes:

>Gary Mills wrote:
>> In <1168454065.954093.268870@p59g2000hsd.googlegroups.com> "bl8n8r" <bl8n8r@yahoo.com> writes:
>>
>> >Gary Mills wrote:
>> ><snip>
>> >> With Solaris 10, this is easier and simpler to do under gdm than under
>> >> dtlogin.  See http://mail.cc.umanitoba.ca/dtautologin/ for one way to
><snip>

>I've installed installed the SUNWcsl* packages to /tmp/ and then just
>copied pam_allow, and the symlink, to /usr/lib/security. Should the
>entire Nevada:SUNWcsl* packages be installed, or will this cause some
>inconsistencies with the rest of the system?

No, don't install the entire package.  All you need is the one
missing file.

>Issuing "/usr/local/sbin/dtautologin start"  seems to just loop [0]
>over starting the Xserver.  Any ideas why this is?   I'll go over the
>install in case I've goofed.

That's the old Solaris 9 way.  You don't need that part.  Just switch
over to gdm instead of dtlogin and see if you can log in manually with
the new window manager.  Once that's working, you can change the
configuration to make it automatic.

-- 
-Gary Mills-    -Unix Support-    -U of M Academic Computing and Networking-

Gary Mills wrote:
<snip>
> That's the old Solaris 9 way.  You don't need that part.  Just switch
> over to gdm instead of dtlogin and see if you can log in manually with
> the new window manager.  Once that's working, you can change the
> configuration to make it automatic.

Just to be clear, I don't have a tube hooked up to this box, so I'm
sshd in to set this all up (if it makes a difference).   I was able to
run gdmconfig over an sshd session and setup the autologin user, and
auto-login feature.  Do I need XDMCP enabled also?  Aferwards, I was
able to choose 'Gnome Session' from another solaris 10 machine on the
network and get a remote login as the autologin user (can start a full
JDS session this way as well).  After resetting the box and letting gdm
startup normally, gdm-binary is the only gdm process running, and the
errors below are in /var/adm/messages.  Any help is welcome.

Thanks


[0]
Jan 12 11:04:18 oas gdm[539]: [ID 702911 daemon.error]
gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Jan 12 11:04:31 oas gdm[548]: [ID 702911 daemon.error]
gdm_slave_xioerror_handler: Fatal X error - Restarting :0
Jan 12 11:04:31 oas gdm[484]: [ID 702911 daemon.error] Failed to start
X server several times in a short time period; disabling display :0

In <1168623185.667491.248680@38g2000cwa.googlegroups.com> "bl8n8r" <bl8n8r@yahoo.com> writes:

>Gary Mills wrote:
><snip>
>> That's the old Solaris 9 way.  You don't need that part.  Just switch
>> over to gdm instead of dtlogin and see if you can log in manually with
>> the new window manager.  Once that's working, you can change the
>> configuration to make it automatic.

>Just to be clear, I don't have a tube hooked up to this box, so I'm
>sshd in to set this all up (if it makes a difference).   I was able to
>run gdmconfig over an sshd session and setup the autologin user, and
>auto-login feature.  Do I need XDMCP enabled also?  Aferwards, I was
>able to choose 'Gnome Session' from another solaris 10 machine on the
>network and get a remote login as the autologin user (can start a full
>JDS session this way as well).  After resetting the box and letting gdm
>startup normally, gdm-binary is the only gdm process running, and the
>errors below are in /var/adm/messages.  Any help is welcome.

You need a frame buffer, monitor, keyboard, and mouse.  Otherwise,
there's no way to set up automatic login with a GUI when the machine
boots.  That's because the whole process has to be initiated from
the newly-booted machine.  (A Sun Ray might be coerced into working,
but not in its normal configuration.)

-- 
-Gary Mills-    -Unix Support-    -U of M Academic Computing and Networking-

Gary Mills wrote:
<snip>
> You need a frame buffer, monitor, keyboard, and mouse.  Otherwise,
> there's no way to set up automatic login with a GUI when the machine
> boots.  That's because the whole process has to be initiated from
> the newly-booted machine.  (A Sun Ray might be coerced into working,
> but not in its normal configuration.)
>

Shoot...  No keyboard, rat or head on this box.  I ended up running
Xvnc listening on
localhost and used that DISPLAY for oracle.  Thanks for all the help
anyway.