zsh-users
 help / color / mirror / code / Atom feed
From: Sweth Chandramouli <sweth@astaroth.nit.gwu.edu>
To: zsh-users@sunsite.auc.dk
Subject: Re: Problem w/ ulimit killing compiles on sol 2.4&2.6 ...
Date: Wed, 3 Feb 1999 13:48:42 -0500	[thread overview]
Message-ID: <19990203134842.C11106@astaroth.nit.gwu.edu> (raw)

On Wed, Feb 03, 1999 at 01:29:10PM -0500, Greg Sylvain wrote:
> Ok. great.
> 
> unlimit worked, well on Sol24 box anyway.  To finish this off then, I have
> a couple last questions :
> 
> 1 - where is the most appropriate place to put the unlimit call (~/.zshenv
> or ~/.zshrc).  I never have been able to figure out what goes where.
> Currently, I only specify my path in ~/.zshenv and everything else is done
> in ~/.zshrc, is this correct ?

	from the comments i have in my zsh startup files:

# Sweth's No-Longer-Very-Portable .zshenv File
# 1st user initialization file, read for all non -f shells.

# Sweth's No-Longer-Very-Portable .zprofile File
# 2nd user initialization file, read for login shells

# Sweth's No-Longer-Very-Portable .zshrc File
# 3rd initialization file, read for interactive shells

# Sweth's No-Longer-Very-Portable .zlogin File
# 4th user initialization file, read for login shells

# .zlogout, sourced before exiting a login shell.
# remember to put some sort of sleep command at
# the end if this should produce user-visible output

	i put most env variables (not just path) in my .zshenv (so that
they are available to scripts that i run in addition to interactive 
sessions), along with limit/unlimit commands (again, so they affect
everything).
	i use .zprofile mainly for starting processes--things that
only need to happen once per "sit down at the computer" session,
regardless of how many actual shell sessions i start.  for example,
i start a fetchmail process (or wake a backgrounded one if it is
already running) to check for mail on other server, and set the
erase key depending on whether i'm logging in from my mac at home,
the console on my sun, or my desktop pc--it's an "environment"
variable, but it's only needed for interactive shells, and then
should stay the same for all of shells spawned from that same
terminal.
	in .zshrc, i set my zshoptions, define aliases, and do
compctl stuff--they are things that mostly affect how the
shell reacts to what i type during an interactive session.
	at the moment, i don't use .zlogin; soon, though, i
hope to move some of the stuff in my .zprofile there, to
take advantage of the functions i define in .zshrc so that
my scripts don't have to be so redundant.  (i could probably
move a lot of the environment definitions from .zshenv here
safely as well, and eliminate a lot more redundancy that way.)
	in .zlogout, i clean up whatever i started (including
killing process i might have started in .zprofile and .zlogin.

	-- sweth.

-- 
Sweth Chandramouli
IS Coordinator, The George Washington University
<sweth@gwu.edu> / (202) 994 - 8521 (V) / (202) 994 - 0458 (F)
<a href="http://astaroth.nit.gwu.edu/~sweth/disc.html">*</a>


             reply	other threads:[~1999-02-03 18:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-03 18:48 Sweth Chandramouli [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-02-05  9:02 Peter Stephenson
1999-02-05  8:28 Bart Schaefer
1999-02-05  6:40 Andrej Borsenkow
1999-02-04 13:11 Peter Stephenson
1999-02-04  8:46 Peter Stephenson
1999-02-03 19:23 Bart Schaefer
1999-02-03 18:29 Greg Sylvain
1999-02-03 18:09 Greg Sylvain
1999-02-03 17:54 Bart Schaefer
1999-02-03 17:38 Greg Sylvain

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=19990203134842.C11106@astaroth.nit.gwu.edu \
    --to=sweth@astaroth.nit.gwu.edu \
    --cc=zsh-users@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).