Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>
> > Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> > ...
> > > I have installed Fedora 8 on another 32bit x86 system, and the problem
> > > appears there too.
> > >
> > > (I moved /etc/csh* out of the w
Jim Meyering <[EMAIL PROTECTED]> writes:
> Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> ...
> > I have installed Fedora 8 on another 32bit x86 system, and the problem
> > appears there too.
> >
> > (I moved /etc/csh* out of the way, used a freshly created account that
> > uses /bin/tc
Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
...
> I have installed Fedora 8 on another 32bit x86 system, and the problem
> appears there too.
>
> (I moved /etc/csh* out of the way, used a freshly created account that
> uses /bin/tcsh. I also deleted all the ~/.* files)
>
> I straced the mingetty proc
Jim Meyering <[EMAIL PROTECTED]> writes:
> Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> > Jim Meyering <[EMAIL PROTECTED]> writes:
> >
> > > Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> > > ...
> > > > I created a new account with /bin/tcsh as a shell, deleted all the
dot
> >
Jim Meyering <[EMAIL PROTECTED]> writes:
> Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> > Jim Meyering <[EMAIL PROTECTED]> writes:
> >
> > > Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> > > ...
> > > > I created a new account with /bin/tcsh as a shell, deleted all the
dot
> >
Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>
> > Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> > ...
> > > I created a new account with /bin/tcsh as a shell, deleted all the dot
> > > files in that new account, logged in on a linux console and run the
Jim Meyering <[EMAIL PROTECTED]> writes:
> Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> ...
> > I created a new account with /bin/tcsh as a shell, deleted all the dot
> > files in that new account, logged in on a linux console and run the
> > perl command above. It prints IGNORE.
> >
Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
...
> I created a new account with /bin/tcsh as a shell, deleted all the dot
> files in that new account, logged in on a linux console and run the
> perl command above. It prints IGNORE.
>
> tcsh is: tcsh-6.14-15
> perl is: perl-5.8.8-23.fc7
Finally! So
Jim Meyering <[EMAIL PROTECTED]> writes:
> Jim Meyering <[EMAIL PROTECTED]> wrote:
>
> > Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> > ...
> >> > Have you tried changing your login shell to bash?
> >>
> >> Yeah, changing the login shell to bash works.
> >> But so does running ba
Jim Meyering <[EMAIL PROTECTED]> wrote:
> Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> ...
>> > Have you tried changing your login shell to bash?
>>
>> Yeah, changing the login shell to bash works.
>> But so does running bash from tcsh and running tcsh from that bash.
>
> I've tried setting my sh
Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
...
> > Have you tried changing your login shell to bash?
>
> Yeah, changing the login shell to bash works.
> But so does running bash from tcsh and running tcsh from that bash.
I've tried setting my shell to tcsh (tcsh-6.15-1.fc8)
but still can't get it
Jim Meyering <[EMAIL PROTECTED]> writes:
> Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
>
> > Jim Meyering <[EMAIL PROTECTED]> writes:
> >
> > > Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> > >
> > > > [EMAIL PROTECTED] (Bob Proulx) writes:
> > > >
> > > > > Dan Nicolaes
Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>
> > Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> >
> > > [EMAIL PROTECTED] (Bob Proulx) writes:
> > >
> > > > Dan Nicolaescu wrote:
> > > > > Paul Eggert writes:
> > > > > > bash -c '(while
Jim Meyering <[EMAIL PROTECTED]> writes:
> Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
>
> > [EMAIL PROTECTED] (Bob Proulx) writes:
> >
> > > Dan Nicolaescu wrote:
> > > > Paul Eggert writes:
> > > > > bash -c '(while echo foo; do :; done); echo status=$? >&2' |
head
> >
Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] (Bob Proulx) writes:
>
> > Dan Nicolaescu wrote:
> > > Paul Eggert writes:
> > > > bash -c '(while echo foo; do :; done); echo status=$? >&2' | head
> > > >
> > > > If it eventually outputs "write error: Broken pipe", yo
[EMAIL PROTECTED] (Bob Proulx) writes:
> Dan Nicolaescu wrote:
> > Paul Eggert writes:
> > > bash -c '(while echo foo; do :; done); echo status=$? >&2' | head
> > >
> > > If it eventually outputs "write error: Broken pipe", you have SIGPIPE
> > > trapped, and that would explai
Dan Nicolaescu wrote:
> Paul Eggert writes:
> > bash -c '(while echo foo; do :; done); echo status=$? >&2' | head
> >
> > If it eventually outputs "write error: Broken pipe", you have SIGPIPE
> > trapped, and that would explain your problem (which you need to track
> > down). If it prin
Paul Eggert <[EMAIL PROTECTED]> writes:
> Dan Nicolaescu <[EMAIL PROTECTED]> writes:
>
> > Nope, nothing.
>
> Can you determine whether processes have SIGPIPE trapped somehow?
> If so, that's the problem; and you can try to track that down.
>
> For example, what does this shell
Dan Nicolaescu <[EMAIL PROTECTED]> writes:
> Nope, nothing.
Can you determine whether processes have SIGPIPE trapped somehow?
If so, that's the problem; and you can try to track that down.
For example, what does this shell command do?
bash -c '(while echo foo; do :; done); echo status=$? >&2' |
[Sorry for the late reply, I've been traveling].
Jim Meyering <[EMAIL PROTECTED]> writes:
> Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
>
> > > > whether to catch SIGPIPE or not. Maybe something has changed in tcsh
> > > > to make it catch SIGPIPE...
> > >
> > > How do you star
Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> This is probably not the right place to talk about this, but since you
> started...
:-)
> bash didn't have decent programmable completion until 3.0 (maybe
That was one of the reasons I switched to zsh.
> 3.1?). It still does not have dabbrev-expand, w
Micah Cowan <[EMAIL PROTECTED]> wrote:
> Jim Meyering wrote:
>> I'm sure you've already heard it, but I have to say it:
>> You shouldn't use csh-based shells.
>> If you ask anyone or google, you'll find many good reasons.
>> Lack of a decent signal-handling mechanism is one of them.
>
> Usually whe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jim Meyering wrote:
> I'm sure you've already heard it, but I have to say it:
> You shouldn't use csh-based shells.
> If you ask anyone or google, you'll find many good reasons.
> Lack of a decent signal-handling mechanism is one of them.
Jim,
Usua
Jim Meyering <[EMAIL PROTECTED]> writes:
> Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> > Jim Meyering <[EMAIL PROTECTED]> writes:
> >
> > > Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> > > > I have been using this alias: lt
Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>
> > Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> > > I have been using this alias: lt = 'ls -lt | head'
> > ...
> > > ls: write error: Brok
Jim Meyering <[EMAIL PROTECTED]> writes:
> Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> > I have been using this alias: lt = 'ls -lt | head'
> ...
> > ls: write error: Broken pipe
> >
> > Is there any reason for this error to be print
Dan Nicolaescu <[EMAIL PROTECTED]> wrote:
> I have been using this alias: lt = 'ls -lt | head'
...
> ls: write error: Broken pipe
>
> Is there any reason for this error to be printed?
Hi Dan,
You should see it only if you have changed the default signal
handling to i
Dan Nicolaescu <[EMAIL PROTECTED]> writes:
> ls: write error: Broken pipe
Most likely you are trapping the PIPE signal. For example:
524-penguin $ ls -lR | head -1
.:
525-penguin $ trap '' PIPE
526-penguin $ ls -lR | head -1
.:
ls: write error: Broken pipe
527-penguin $
0.0*
lrwxrwxrwx 1 root root 20 2007-10-11 06:54 libsvn_wc-1.so.0 ->
libsvn_wc-1.so.0.0.0*
lrwxrwxrwx 1 root root 26 2007-10-11 06:54 libsvn_ra_local-1.so.0 ->
libsvn_ra_local-1.so.0.0.0*
ls: write error: Broken pipe
Is there any reason for this error to be printed?
The st
29 matches
Mail list logo