zsh-users
 help / color / mirror / code / Atom feed
From: mneptok <mneptok@mneptok.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-users@sunsite.dk
Subject: Re: zsh login coredump
Date: Sat, 21 May 2005 20:15:45 -0700	[thread overview]
Message-ID: <1116731745.6855.13.camel@localhost.localdomain> (raw)
In-Reply-To: <050521171740.ZM9619@candle.brasslantern.com>

On Sat, 2005-05-21 at 17:17 -0700, Bart Schaefer wrote:

> Did it occur to you to look at /etc/profile line 33 or perhaps at
> /etc/profile.d/krb5.sh line 5, to see what's causing the parse errors?
> 
> Has /etc/profile or /etc/profile.d/krb5.sh changed recently?  Why?

Yes, it did occur to me, but nothing jumped out at me:

=====
profile
=====

32 # Path manipulation
33 if [ `id -u` = 0 ]; then
34         pathmunge /sbin
35         pathmunge /usr/sbin
36         pathmunge /usr/local/sbin

=====
krb5.sh
=====

1 if ! echo ${PATH} | grep -q /usr/kerberos/bin ; then
2         PATH=/usr/kerberos/bin:${PATH}
3 fi
4 if ! echo ${PATH} | grep -q /usr/kerberos/sbin ; then
5         if [ `id -u` = 0 ] ; then
6                 PATH=/usr/kerberos/sbin:${PATH}
7         fi
8 fi
=====

./k

kurt von finck
-- 
http://www.mneptok.com
mneptok@mneptok.com
--
public key at: subkeys.pgp.net
server key id: 5229D26A
fingerprint: 127A A484 ADBF A5AD E7FB 8CD2 8913 18F4 5229 D26A
--
Success is more a function of consistent common sense than it is of
genius. - An Wang
--


  reply	other threads:[~2005-05-22  3:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-21 23:23 mneptok
2005-05-22  0:17 ` Bart Schaefer
2005-05-22  3:15   ` mneptok [this message]
2005-05-22  6:04     ` Bart Schaefer
2005-05-22  6:20       ` mneptok
2005-05-22 15:38         ` Bart Schaefer
2005-05-23  8:37           ` mneptok
2005-05-23 16:07             ` Bart Schaefer

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=1116731745.6855.13.camel@localhost.localdomain \
    --to=mneptok@mneptok.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-users@sunsite.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).