Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: "Curt, WE7U" <archer@eskimo.com>
To: Bud Rogers <budr@netride.net>
Cc: Linux-hams List <linux-hams@vger.kernel.org>
Subject: Re: Run app on login
Date: Mon, 15 Nov 2004 07:44:56 -0800 (PST)	[thread overview]
Message-ID: <Pine.SUN.4.58.0411150742470.171@eskimo.com> (raw)
In-Reply-To: <200411132106.58898.budr@netride.net>

On Sat, 13 Nov 2004, Bud Rogers wrote:

> On Saturday 13 November 2004 20:47, Chuck Hast wrote:
> > Folks,
> > I am trying to figure out how to have a particular application start
> > up when a user logs in with a specified login.
> > Example,
> > User logs in with "radio"  password "hamradio"
> > Instead of bringing up a prompt, I want a login of radio to start up
> > a special application. I am sure that Linux can do it, just not quite
> > sure how to do so.
>
> Anything you put in a user's .bashrc or .bash_profile will be run
> whenever that user logs in.  You can have it set up things in your
> environment, or run certain commands.  Man bash will give you the
> details.

Or .profile.

Run when logging in:  .profile or .bash_profile

Run when any new shell/subshell is started:  .bashrc

If you're dealing with an environment where one process or one user
might start multiple shells or subshells, then you want to stick
with the .profile or .bash_profile files, as then your application
will only get run once per login.

--
Curt, WE7U			         http://www.eskimo.com/~archer
"Lotto:    A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"

      parent reply	other threads:[~2004-11-15 15:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-14  2:47 Run app on login Chuck Hast
2004-11-14  3:06 ` Bud Rogers
2004-11-14  3:53   ` Curt Mills
2004-11-14 18:44     ` Jim Bayer
2004-11-14 23:53       ` Chuck Hast
2004-11-15 15:44   ` Curt, WE7U [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.SUN.4.58.0411150742470.171@eskimo.com \
    --to=archer@eskimo.com \
    --cc=budr@netride.net \
    --cc=linux-hams@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox