Rats. I just double checked, and the CAM scripts
do look explicitly in /usr/dt/config/Xsession.d,
not /etc/dt/config/Xsession.d
I knew we deliberately diverged from standard
session startup for CAM, because you don't want a
typical environment in a CAM session, but forgot
this particular aspect of the divergence.
So, for a normal session /etc/dt/config/Xsession.d
is better, but like my CAM doc says, in CAM you
need to use /usr/dt/config/Xsession.d/*.SUNWut.
It would probably be a bit better if SRSS used
/etc/dt/config/Xsession.d for CAM, but it's also
probably not a big deal since you add your own
scripts anyway and nothing deals with this
directory wholesale during patches etc.
-Bob
Bob Doolittle wrote:
Jim Klimov wrote:
Hello Mike,
MC> But the moment that person logs off, power cycles the SunRay,
etc; the
MC> permissions are
MC> reset and the printer is owned only by that local user. No one else
MC> can print directly to the device.
MC> Surely there is a way to do this that is simple. What am I missing?
Jus my 2 bits...
Bob Doolittle's AMGH Guide points out that there's a way to insert
"startscripts" to every session startup:
...To use it, install utpamclient somewhere, and install a wrapper
for it in /usr/dt/config/Xsession.d/0200.SUNWut (for example - any
name *.SUNWut will do). Make sure the script has execute
permissions set. This will be executed during every session
startup.
You can try to make a script which does chmod 666 on the printer
device (perhaps by a wildcard mask?) and call it from session startup.
You can also try to do the chmod from /etc/profile or a similar
profile script, or from cron.
See my previous post regarding using an standard
lp queue. But if you can't do that, and you want
to try something like the above, read the dtlogin
man page. It describes several points where you
can instrument as suggested above:
/usr/dt/config/Xsetup (run as root immediately before a login
greeter is displayed)
/usr/dt/config/Xstartup (run as root immediately after the user
authenticates)
/etc/dt/config/Xsession.d/* (scripts run as the user immediately after
Xstartup
but before the user's desktop session begins)
/usr/dt/config/Xreset (run as root upon logging out before the session
exits)
Xsession.d is most modular since you can write
your own script and add it to the directory. This
isolates you best against future patches etc. You can
put a script into /usr/dt/config/Xsession.d/* also but
/etc/dt/config/Xsession.d/* is preferred (I updated my
blog reference).
The dtlogin man page suggests you should copy
/usr/dt/config/{Xsetup,Xstartup,Xreset} to
/etc/dt/config before modifying them, to isolate
yourself from future dtlogin patches. However, if
you do so SRSS won't update them properly, so be
sure to fold in any SRSS changes if you do this.
SRSS only updates the versions in /usr/dt/config,
since Sun software is not supposed to touch
/etc/dt/config files.
-Bob
_______________________________________________
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
