UNIX for Advanced & Expert Users

hi guys,
just went thru a "how to" manual on Solaris CDE....
could any of you pleaz tell me how to restrict users from logging in at
particular times....
in linux,i wrote an access script, put in in /etc/profile and was able t o
restrict users from logging in at particular times on particular days... .{
didnt use PAM }
but its not working in Solaris....
the X session gets killed but still the user is thrown at the shell
prompt..as in fail safe mode....
any ideas how to go about this???

the prob is:-
there are "N" no. of users and every one has a particular fixed time slo t
given on a particular fixed day,,,to access the services....
users shouldnt be able to log in in their unscheduled times.....
also i should be able to keeptrack of the time user is logged in...so as
to display a warning message before his/her slot gets over on that
day.....my script is working fine in linux...from shell prompt as well as
X-prompt.....but..its not working in solaris...???
infact i am not able to figure out where cud i call this script
from....and why doesnt the user log off { 'have tried Kill -9 -1 ,
exit , logout etc } instead of being thrown at
the prompt................

hope you ppl could help me out.....
Regards
Swordfish
p.s. how can one display messages on X-window????..i mean user shouldn,t
just be denied acces..without telling him/her the reason???
I posted the same thread in another forum...my apologies

Maybe you could try this... have the script that validates the user return an exit code depending on whether the user should have access or not; 0 for access and 1 for no access (maybe.. you can decide your return codes) and in each users .profile, write exit on receiving a 1 from the validation script.

I know that this may be a lot of work if you have a lotta users, but this is just off the top of my head

thats ok...
but my point is not only this exiting stuff.............
what i am not sure about is the following:-

1) where to put the validation script in Solaris ..i.e what is the equivalent for /etc/profile in solaris

2) why r the two unix systems behaving differently for kill -9 -1 and exit ?????
{ linux nd solaris }

swordfish

... solaris does use /etc/profile (as does other *nixes) ... why kill behaves differently in linux compared to solaris is most likely because of how each os handles signals to processes ...

if your validation script doesn't work from /etc/profile ... you can also have a sleeping daemon script that checks for users and validates their access hours against a table and then sends pop-ups to users based on your requirements and/or terminates their session ...

if you set the display to the user's desktop ... you can have an xterm window pop-up and warn the user about his or her access through "xterm -e" (see man xterm)

hey,
ya it does have /etc/profile....
but my users by default have Csh as default shell and not bash....
my default shell is /bin/sh
so scripts in /etc/profile wont work because its not sourced....
the first file that gets sourced is /usr/dt/bin/Xsession for logins through common desktop environment [ CDE ] Solaris............
and my problem is...any script call from here doesnt work...
eg i added this line in it

if [ $LOGNAME -ne root ]
then
/etc/access.sh
fi

but it just isnt working ..............

and ya ..regarding daemon script.......how is it gonna be different from a normal script...and how m i gonna start it at the first place.... i mean from where should i source it.

a daemon script is really no different than a normal script except for how it "functions" ... in this case, "nothing" calls it, it starts "by itself," and it does it's work in the background ... you can start it from cron or from a startup script in /etc/rc3.d (check other scripts there for formatting) so it starts up after every reboot ...

there is file called .dtprofile in every users who has authority to use Xsession in the CDE environment for *nixes.


Within this file there is a line called

# DTSOURCEPROFILE=true

uncomment this line will enable the usage of the .profile of the particular user.
This will in turn make either your .profile or .cshrc available and you can code the validation of the users restrictions in the startup scripts.

Hope this helps.


Jerardfjay