[aklug] Re: terminal types and curses programming

On Mon, 26 Jan 2009, Arthur Corliss wrote:

> My suggestion was not to call the program from your shell rc scripts, but to
> use it as a shell itself. If you want to do it that way, though, make sure
> you're using 'trap' to disable signals before the program is executed, and
> then use 'exit' after calling your program. That ensures the shell is
> exited regardless of how your program is terminated.
>

I just tried this with one of my accounts on my testing server, using
chsh. Seems to work great -- more natural that calling it from an rc
script. I also added the program to /etc/shells like Shane suggested.

I'm going to sound like a real noob here, but can you explain a bit more
about the 'trap' and 'exit' part? Is this something I'm supposed to add to
some init script or something? (I'll read the man pages if you'll point me
to the right ones.)

Another question: Does having my program as the user's default login shell
have any other drawbacks (that is, since the program isn't really a
shell). It doesn't matter to other programs what the default shell is, or
does it?

-- 
Christopher Howard
http://indicium.us
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.