TIP: Click on subject to list as thread! ANSI
echo: cis.os9.68000.osk
to: all
from: Bob van der Poel 76510,2203
date: 1993-04-11 22:43:07
subject: #login

#: 17895 S12/OS9/68000 (OSK)
    11-Apr-93  22:43:07
Sb: #login
Fm: Bob van der Poel 76510,2203
To: all

I've been setting up my system to use login, instead of just booting with a
startup file. I have got tsmon running from startup to monitor the terminal
posts. This works fine. However, I would like to force anyone just turning on
the computer to go though login as well. I can do this by sticking a login
command in the startup file...however, everything past the command gets
ignored. Since, I want to set up some extra windows...this is not good. I can't
set the windows first; that would eliminate the security of login. Seems that I
am in a catch-22 situation.

Next, I figured that I'd give each user his own directory. And to make it hard
for other users to examine the files of others I also figured I'd set the
access permissions of the directories to prevent public read/write. No good.
The first thing login does is try to chd to the directory. But, if the
directory does NOT have public read/write then it can't do so. Frankly, this
doesn't make sense to me since login is running in superuser mode. Is there a
way around this one?

There are 2 Replies.

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.