Thank you for the prompt reply! Unfortunatelly, I can't open a local
console, the box has VGA output and I have no VGA monitor. So, SSH is
the only option. But I do can boot a clean SQUEEZE system, mount the
root file system of the broken JESSIE system and download log files.
What information
problems, and also let me to connect over SSH. But after 1-2
minutes the client terminal freezes and the outputs this error message:
packet_write_wait: Connection to 192.168.1.2: Broken pipe. The network
activity LED on the box is flushing permanently. After that, no more
connections are accepted
. The last two, wheezy and jessie, start
without problems, and also let me to connect over SSH. But after 1-2
minutes the client terminal freezes and the outputs this error message:
packet_write_wait: Connection to 192.168.1.2: Broken pipe. The network
activity LED on the box is flushing
On Fri, 2015-06-05 at 20:50 +0200, SkyFish wrote:
Thank you for the prompt reply! Unfortunatelly, I can't open a local
console, the box has VGA output and I have no VGA monitor.
Buy an adapter! ;)
So, SSH is
the only option. But I do can boot a clean SQUEEZE system, mount the
root file
'/usr/lib/libDOM.so.4.9.24', which is also in
package libsope-xml4.9 4.9.r1664.20140307
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/libsope1_2.2.5-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error
to overwrite '/usr/lib/libDOM.so.4.9.24', which is also in
package libsope-xml4.9 4.9.r1664.20140307
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/libsope1_2.2.5-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned
On Tue, Jul 01, 2014 at 03:08:54AM +0200, Tamer Higazi wrote:
Hi people!
I really don't know, how to solve this problem. Does any of you have an
idea ?!
root@babe3306:/home/tamer# apt-get install -f
Preparing to unpack .../libsope1_2.2.5-1_amd64.deb ...
Unpacking libsope1 (2.2.5-1) ...
esclavos, 192.168.2.19(Centos) y 192.168.2.21(Ubuntu). El
primero tiene como gateway a 192.168.0.2 y el segundo a 192.168.2.1.
Con Ubuntu ningún problema con el trafico de red pero con Centos
aleatoriamente ocurre un broken pipe de una sesión ssh, lo único que se me
ocurrió despues de días dando
broken pipe de una sesión ssh, lo único que se
me
ocurrió despues de días dando cabezasos es pasar ese nodo Centos a la
subred
con ip 192.168.0.9 y todo arreglado. Abajo pegaré el log de un broken
pipe.
¿Hay alguna idea para en esta situación se produzca un broken pipe? Y he
configurado Centos para
a 192.168.0.2 y el
segundo a 192.168.2.1.
Dices que el CentOS tiene IP 192.168.2.19 y gateway 192.168.0.2. ¿La
gateway del CentOS no debería ser también 192.168.2.1 si está en dicha red?
Con Ubuntu ningún problema con el trafico de red pero con Centos
aleatoriamente ocurre un broken pipe de una
(Ubuntu). El
primero tiene como gateway a 192.168.0.2 y el segundo a 192.168.2.1.
Con Ubuntu ningún problema con el trafico de red pero con Centos
aleatoriamente ocurre un broken pipe de una sesión ssh, lo único que se me
ocurrió despues de días dando cabezasos es pasar ese nodo Centos a la subred
con
aleatoriamente ocurre un broken pipe de una sesión ssh, lo único que se
me ocurrió despues de días dando cabezasos es pasar ese nodo Centos a la
subred con ip 192.168.0.9 y todo arreglado. Abajo pegaré el log de un
broken pipe.
Como dice Camaleón me parece raro que sea por culpa de una ruta pero
creo
que el CentOS tiene IP 192.168.2.19 y gateway 192.168.0.2. ¿La
gateway del CentOS no debería ser también 192.168.2.1 si está en dicha red?
Con Ubuntu ningún problema con el trafico de red pero con Centos
aleatoriamente ocurre un broken pipe de una sesión ssh, lo único que se
me ocurrió despues
trafico de red pero con Centos
aleatoriamente ocurre un broken pipe de una sesión ssh, lo único que se
me ocurrió despues de días dando cabezasos es pasar ese nodo Centos a la
subred con ip 192.168.0.9 y todo arreglado. Abajo pegaré el log de un
broken pipe.
¿Hay alguna idea para en esta situación
ningún problema con el trafico de red pero con Centos
aleatoriamente ocurre un broken pipe de una sesión ssh, lo único que se
me ocurrió despues de días dando cabezasos es pasar ese nodo Centos a la
subred con ip 192.168.0.9 y todo arreglado. Abajo pegaré el log de un
broken pipe.
(...)
El
that even though the command produces no output you then get broken
pipe? If so the connection is likely being terminated because it's idle
(check your internet provider). The keepalive should prevent this.
If you log in and do a
ls -R /
do you get the output or broken pipe? If you get broken pipe
no output you then get broken
pipe? If so the connection is likely being terminated because it's idle
(check your internet provider). The keepalive should prevent this.
If you log in and do a
ls -R /
do you get the output or broken pipe? If you get broken pipe before the
command completes
server, I get
kicked out of my ssh session with a Write failed: Broken pipe error.
I've seen that before and it took us ages to narrow down - in our case
(admittedly your case may be different), it was the combination of
network interface MTU and packet fragmentation. Reducing the MTU on
our
back-and-forth
traffic. My ISP is a mobile phone network over 3G so they are probably
trying to keep the bandwidth for phones only.
I do -o ServerAliveInterval=5 which has my ssh client ping the server
every 5 seconds to keep it alive.
To summarise, I get rid of broken pipe errors
Karl E. Jorgensen karl.jorgen...@nice.com wrote:
I've seen that before and it took us ages to narrow down - in our case
(admittedly your case may be different), it was the combination of
network interface MTU and packet fragmentation.
I was just going to suggest exactly the same thing. And it
I'm connecting at various times to different Debian/Squeeze servers from
my Debian/Wheezy workstation using ssh. No matter which server I connect
to, I find that if I move a lot of data on the remote server, I get
kicked out of my ssh session with a Write failed: Broken pipe error
the bandwidth for phones only.
I do -o ServerAliveInterval=5 which has my ssh client ping the server
every 5 seconds to keep it alive.
To summarise, I get rid of broken pipe errors by using this command line
ssh -o ServerAliveInterval=5 u...@server.com
Hope this helps,
elbbit
--
elb
3G so they are probably
trying to keep the bandwidth for phones only.
I do -o ServerAliveInterval=5 which has my ssh client ping the server
every 5 seconds to keep it alive.
To summarise, I get rid of broken pipe errors by using this command line
ssh -o ServerAliveInterval=5 u...@server.com
Hope
. My ISP is a mobile phone network over 3G so they are probably
trying to keep the bandwidth for phones only.
I do -o ServerAliveInterval=5 which has my ssh client ping the server
every 5 seconds to keep it alive.
To summarise, I get rid of broken pipe errors by using this command line
ssh -o
if there is too little back-and-forth
traffic. My ISP is a mobile phone network over 3G so they are probably
trying to keep the bandwidth for phones only.
I do -o ServerAliveInterval=5 which has my ssh client ping the server
every 5 seconds to keep it alive.
To summarise, I get rid of broken pipe errors
. My ISP is a mobile phone network over 3G so they are probably
trying to keep the bandwidth for phones only.
I do -o ServerAliveInterval=5 which has my ssh client ping the server
every 5 seconds to keep it alive.
To summarise, I get rid of broken pipe errors by using this command line
ssh -o
PROTECTED]:~$
bash, csh, ksh, sh, tcsh - alle kaputt.
Die tcsh, liefert zumindest noch ne Fehlermeldung pro versuchten
Aufruf: broken pipe.
Ich kann leider nicht erruieren in welchem Paket das Problem auftaucht.
ldap, pam, login, tty, libnss - keine Ahnung.
Wo könnt ich diesen fiesen Bug denn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Iñaki wrote:
Servidor de correo a medida? De que estas hablando?
Cuanto tiempo, esfuerzo y trabajo te lleva implementar y dejar
funcionando con mantenimiento cercano a cero eso que te plantee?
Me explico: una cosa es dejar el servidor
El Lunes, 6 de Marzo de 2006 13:23, Ricardo Frydman Eureka! escribió:
Iñaki wrote:
Servidor de correo a medida? De que estas hablando?
Cuanto tiempo, esfuerzo y trabajo te lleva implementar y dejar
funcionando con mantenimiento cercano a cero eso que te plantee?
Me explico: una cosa es
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Antonio Galicia wrote:
On 3/3/06, Ricardo Frydman Eureka! [EMAIL PROTECTED] wrote:
PD: Aprovecho para decir que en Linux no existe ningún servidor de correo
como
solución final (SMTP, POP, IMAP, autenticación, reglas, interfaz web de
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Iñaki wrote:
El Viernes, 3 de Marzo de 2006 16:25, Ricardo Frydman Eureka! escribió:
Iñaki wrote:
PD: Aprovecho para decir que en Linux no existe ningún servidor de correo
como solución final (SMTP, POP, IMAP, autenticación, reglas, interfaz web
On 3/4/06, Ricardo Frydman Eureka! [EMAIL PROTECTED] wrote:
small is beatifull
Supongo entonces que el proyecto gnome te parece una aberración. Y
mejor ni hablar de mono.
Filosofia *nix: hacer una sola cosa bien y eficientemente.
Filosofia GNU/FLOSS: Libertad de eleccion/variedad de gustos
El Sábado, 4 de Marzo de 2006 15:27, Ricardo Frydman Eureka! escribió:
ese no es de los buenos, que
use soluciones integradas y finales de Microsoft o que pague a un
consultor para que le diseñe un servidor de correo a medida.
Servidor de correo a medida? De que estas hablando?
Cuanto
: couldn't write 72 items to {standard output}:
Broken pipe: error de escritura: Tuberia rota
--
Pero repito, el el error NO sucede si ejecuto manualmente el script con un
correo como parámetro de CUALQUIER
=- FNR=139) fatal: print to
standard output failed (Broken pipe)\ncat: error de escritura: Tuber\237a
rota\n
Pero repito, el el error NO sucede si ejecuto manualmente el script con
un correo como parámetro de CUALQUIER tamaño, sólo sucede si lo ejecuta
CommuniGate con correos GRANDES (de
)
action #1:
execute stderr: sed: couldn't write 72 items to {standard output}:
Broken pipe: error de escritura: Tuberia rota
-
-
Pero repito, el el error NO sucede si ejecuto manualmente el
ENQUEUERRULES [9570439] rule(myRule)
action #1:
execute stderr: sed: couldn't write 72 items to {standard output}:
Broken pipe: error de escritura: Tuberia rota
-
-
Pero repito, el el error NO sucede si
On 3/3/06, Ricardo Frydman Eureka! [EMAIL PROTECTED] wrote:
PD: Aprovecho para decir que en Linux no existe ningún servidor de correo
como
solución final (SMTP, POP, IMAP, autenticación, reglas, interfaz web de
mantenimiento y configuración con Logs, gráficas y demás reportes, todo ello
El Viernes, 3 de Marzo de 2006 16:25, Ricardo Frydman Eureka! escribió:
Iñaki wrote:
PD: Aprovecho para decir que en Linux no existe ningún servidor de correo
como solución final (SMTP, POP, IMAP, autenticación, reglas, interfaz web
de mantenimiento y configuración con Logs, gráficas y
Hola.
Estoy desarrollando para una empresa unos pequeños scripts a medida para
complementar a un servidor de correo propietario (CommuniGate) y dotarle de
funcionalidades que requieren.
Básicamente existen unas Queue Rules es las que puedes definir una Action
que sea ejecutar un programa
On 3/2/06, Iñaki [EMAIL PROTECTED] wrote:
Un problema similar sucede si uso awk en vez de sed:
cat $correo_original | awk 'ok{print}/^\s*$/{ok=1}' | formail -X
$cabecera_original
' | formail -X $cabecera_original
el error sería éste:
11:23:54.64 1 ENQUEUERRULES [9570439] rule(myRule) action #1:
execute stderr: sed: couldn't write 72 items to {standard output}:
Broken pipe: error de
On 3/2/06, Iñaki [EMAIL PROTECTED] wrote:
Un problema similar sucede si uso awk en vez de sed:
-
--- cat $correo_original | awk
'ok{print}/^\s*$/{ok=1}' | formail -X
Kevin B. McCarty wrote:
Hi Scott,
Scott wrote:
But seriously folks...
What's a broken pipe?
A pipe is this keyboard symbol: |
That part I knew. :-)
When you want to use the output of one command as the input of another
command, you pipe it, like this: ls -l | sort
And that part too
Hi Scott,
Scott wrote:
But seriously folks...
What's a broken pipe?
A pipe is this keyboard symbol: |
When you want to use the output of one command as the input of another
command, you pipe it, like this: ls -l | sort
A broken pipe happens when the command reading input dies unexpectedly
I have sarge running with the dcc-client and spamd running. I have been
getting the following messages in my syslog - they appear after spamd
completes processing the message:
Dec 2 07:20:30 debian dccifd[5800]: write(MTA socket,88): Broken pipe
Note that this does not appear after every
', which
is also in package asterisk
-sounds-extra
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/asterisk-sounds-amportal_1.10.009-42_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
---
and I can't install any
On Mon, Nov 28, 2005 at 05:32:09PM +0800, Marcus Deluigi (intern) wrote:
trying to overwrite `/usr/share/asterisk/sounds/ext-or-zero.gsm', which
is also in package asterisk
^^^ the package conflicts with `asterisk'.
and I can't install any other packages anymore, because apt-get reports
(intern) wrote:
trying to overwrite `/usr/share/asterisk/sounds/ext-or-zero.gsm',
which is also in package asterisk
^^^ the package conflicts with `asterisk'.
and I can't install any other packages anymore, because apt-get
reports unmet dependencies:
---
The following
On Mon, Nov 28, 2005 at 05:32:09PM +0800, Marcus Deluigi (intern) wrote:
Hi!
I tried to install an unofficial debian package (AMPortal) by adding a
new ressource to resources.list.
But the installation failed with the error message:
[...]
The problem is that your unofficial package
: device: default
** WARNING **: ctrl_write_packet(): Failed to send data: Broken pipe
#--
Next, I played the file with mplayer and it worked perfectly:
#--
$ mplayer -playlist listen.m3u
#--
So
command line and got this error (and the dialog box
saying couldn't connect to host):
#--
$ xmms listen.m3u
Message: device: default
** WARNING **: ctrl_write_packet(): Failed to send data: Broken pipe
#--
Next, I played
On Wed, 09 Nov 2005 17:52:21 -0500
H.S. [EMAIL PROTECTED] wrote:
H.S. wrote:
Hi,
I am having trouble since looong to make xmms play m3u playlist
files. Here is the problem:
If I click on an m3u link on a webpage in mozilla, xmms starts but
gives an error: Couldn't connect to host
killed by signal (Broken Pipe)
Any Ideas how to work around?
--
Regards, Dave
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Am Donnerstag, 18. November 2004 00:36 schrieb Jochen von der Wall:
Am Mittwoch, 17. November 2004 21:33 schrieb Michael Bienia:
Gute Frage.
Welche Ausgabe erhälst du bei
dpkg -l 'libuuid1*'
# dpkg -l 'libuuid1*'
Desired=Unknown/Install/Remove/Purge/Hold
to overwrite `/lib/libuuid.so.1.2', which is also in package
libuuid1-udeb
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
/cdrom//pool/main/e/e2fsprogs/libuuid1_1.35-6_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Was muß ich
/e2fsprogs/libuuid1_1.35-6_i386.deb
(--unpack):
trying to overwrite `/lib/libuuid.so.1.2', which is also in package
libuuid1-udeb
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
/cdrom//pool/main/e/e2fsprogs/libuuid1_1.35-6_i386.deb
E: Sub
Am Mittwoch, 17. November 2004 18:31 schrieb Michael Bienia:
Bugreport schreiben ist das beste. Es gibt die Moeglichkeit mittels
dpkgs --force-Option zu arbeiten, aber IMHO ist es noetig den
Maintainer zu informieren, schliesslich ist das ein ziemlich grober
Fehler. Wobei es mich wundert,
On 17.Nov 2004 - 18:31:42, Michael Bienia wrote:
Was hier wurdert ist das udeb. Soviel ich weiß werden die nur vom
Debian-Installer genutzt und haben auf einem normalen System nichts
verloren.
Ich kenne den Debian-Installer ja nun ueberhaupt nicht und dachte,
dass der diese udeb's beim
On 2004-11-17 19:31:18 +0100, Andreas Pakulat wrote:
On 17.Nov 2004 - 18:31:42, Michael Bienia wrote:
Was hier wurdert ist das udeb. Soviel ich weiß werden die nur vom
Debian-Installer genutzt und haben auf einem normalen System nichts
verloren.
Ich kenne den Debian-Installer ja nun
On 2004-11-17 19:17:06 +0100, Jochen von der Wall wrote:
Am Mittwoch, 17. November 2004 18:31 schrieb Michael Bienia:
Bugreport schreiben ist das beste. Es gibt die Moeglichkeit mittels
dpkgs --force-Option zu arbeiten, aber IMHO ist es noetig den
Maintainer zu informieren,
Am Mittwoch, 17. November 2004 21:33 schrieb Michael Bienia:
Gute Frage.
Welche Ausgabe erhälst du bei
dpkg -l 'libuuid1*'
# dpkg -l 'libuuid1*'
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/
.
Permission denied, please try again.
Permission denied (publickey,password,keyboard-interactive).
$
Quando executo o ssh com um ssh-agent no ar (eval `ssh-agent`),
$ ssh [EMAIL PROTECTED]
ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory
Write failed: Broken pipe
$
Porém quando
executo o ssh com um ssh-agent no ar (eval `ssh-agent`),
$ ssh [EMAIL PROTECTED]
ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory
Write failed: Broken pipe
$
Porém quando adiciono a chave ao ssh-agent (ssh-add), a autenticação
funciona direitinho.
Isso começou a ocorrer depois
Em Qui, 2003-02-06 às 02:28, RC Lages escreveu:
dpkg: erro processando
/var/cache/apt/archives/kdebase-bin_4%3a3.1.0-0woody2_i386.deb
(--unpack):
tentando sobrescrever `/usr/bin/kdcop', que também está no pacote kdcop
dpkg-deb: subprocesso paste morto por sinal (Broken pipe)
Erros foram
/kdcop', que também está no pacote kdcop
dpkg-deb: subprocesso paste morto por sinal (Broken pipe)
Erros foram encontrados durante processamento de:
/var/cache/apt/archives/kdebase-bin_4%3a3.1.0-0woody2_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
debian:/home/lages#
Alguém sabe
Am Montag dem 22. Apr 2002 um 23:42 +0200 Uhr, meinte Hannes Lau:
Hallo,
Neustart dies: Die telnet-verbindung zum Rechner ist aeusserst lahm,
aber nur beim Verbindungsaufbau...
Also ich beobachte das derzeit. Nachdem ich den Rechner ueber Nacht
mit Nichtbeachtung strafte und einem Neustart
). Aus den log´s kommt dies:
---
Apr 22 22:40:15 penti100 in.telnetd[576]: connect from
penti600.lau.debitel.net
Apr 22 22:40:35 penti100 telnetd[576]: ttloop: read: Broken pipe
Apr 22 22:40:40 penti100 in.telnetd[577]: connect from
penti333.hannes.linux
---
Wo muss ich da ansetzen, um das Problem zu
Broken pipe)
E: Failure running sript /usr/sbin/dpkg-preconfigure --apt
sid:~#
Nevere ran into an error of this type. Should have I upgraded to woody
first, then unstable? Any suggestions appreciated.
: cannot open
shared object file: No such file or directory
E: Write error - write (32 Broken pipe)
E: Failure running sript /usr/sbin/dpkg-preconfigure --apt
sid:~#
It is not finding some perl modules that it needs. The required packages are
probably in your cache. I suggest trying
: cannot open
shared object file: No such file or directory
E: Write error - write (32 Broken pipe)
E: Failure running sript /usr/sbin/dpkg-preconfigure --apt
sid:~#
Nevere ran into an error of this type. Should have I upgraded to woody
first, then unstable? Any suggestions appreciated.
Hello
of archives. After unpacking 13.0MB will be
used.
Do you want to continue? [Y/n]
perl: error while loading shared libraries: libdb.so.3: cannot
open
shared object file: No such file or directory
E: Write error - write (32 Broken pipe)
E: Failure running sript /usr/sbin/dpkg-preconfigure
or directory
E: Write error - write (32 Broken pipe)
E: Failure running sript /usr/sbin/dpkg-preconfigure --apt
sid:~#
Nevere ran into an error of this type. Should have I upgraded to woody
first, then unstable? Any suggestions appreciated.
Hello,
I had these problems with perl when upgrading
In attempting to dpkg -i libgtk1.2_1.2.6-1.deb, the current potato
libgtk, I'm getting the following:
dpkg-deb: subprocess paste killed by signal (Broken pipe)
dpkg: error processing libgtk1.2_1.2.6-1.deb) ...
subprocess dpkg-deb --fsys-tarfile returned error exit status 2
Could someone please
--- [EMAIL PROTECTED] wrote:
In attempting to dpkg -i libgtk1.2_1.2.6-1.deb, the current potato
libgtk, I'm getting the following:
dpkg-deb: subprocess paste killed by signal (Broken pipe)
dpkg: error processing libgtk1.2_1.2.6-1.deb) ...
subprocess dpkg-deb --fsys-tarfile returned error
:
/etc/cron.daily/popularity-contest:
/usr/bin/dpkg-awk: line 31: 2988 Broken pipe mawk $incf -f
+/usr/lib/awk/dpkg-awk.lib -- --exebase=`basename $0` --exedir=`dirname
$0`
+$@
I installed popularity-contest (stable) on my machine and every day I get
the following message from cron:
/etc/cron.daily/popularity-contest:
/usr/bin/dpkg-awk: line 31: 2988 Broken pipe mawk $incf -f
+/usr/lib/awk/dpkg-awk.lib -- --exebase=`basename $0` --exedir=`dirname $0
On Sun, 22 Mar 1998 [EMAIL PROTECTED] wrote:
** Reply to note from Art Lemasters [EMAIL PROTECTED] Mon, 23 Mar 1998
00:20:29 -0600 (CST)
default, or my bo was broken. In any case, less was an excellent idea
for a default for manpage paging.
Quite honestly I can't think of
I get this:
[79 jacinta:~] while true ; do echo -n . ; /usr/sbin/update-alternatives
--display WindowMaker | grep -q 'WindowMaker-newstyle' ; done
.Broken pipe
..Broken pipe
..Broken pipe
...Broken pipe
..^C
do you see a problem with the statement? (It's just for test purposes, I'm
only
Broken pipe means that the '| did not recieve any data.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
will be everywhere.
Art
Shaleh enlightened:
Broken pipe means that the '| did not recieve any data.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Sun, 22 Mar 1998, Art Lemasters wrote:
Some wonderful developer(s) fixed our manpage readers of
the coming release (hamm) so that they will also scroll upwards
to the beginning of any file we read. The manpages (accessed
by typing man nameofcommand--without the quotes) can also be
Adam wrote the enlightenment:
On Sun, 22 Mar 1998, Art Lemasters wrote:
Some wonderful developer(s) fixed our manpage readers of
the coming release (hamm) so that they will also scroll upwards
to the beginning of any file we read. The manpages (accessed
by typing man
Addressed to: Art Lemasters [EMAIL PROTECTED]
Debian debian-user@lists.debian.org
** Reply to note from Art Lemasters [EMAIL PROTECTED] Sun, 22 Mar 1998
23:41:26 -0600 (CST)
Some wonderful developer(s) fixed our manpage readers of
the coming release (hamm) so
** Reply to note from Art Lemasters [EMAIL PROTECTED] Mon, 23 Mar 1998
00:20:29 -0600 (CST)
default, or my bo was broken. In any case, less was an excellent idea
for a default for manpage paging.
Quite honestly I can't think of any DOS, Windows or OS/2 text file viewer
program
On Sun, 22 Mar 1998, Art Lemasters wrote:
Some wonderful developer(s) fixed our manpage readers of
the coming release (hamm) so that they will also scroll upwards
to the beginning of any file we read. The manpages (accessed
by typing man nameofcommand--without the quotes) can
On Mon, Mar 23, 1998 at 10:37:39AM +0100, E.L. Meijer (Eric) wrote:
in bask/ksh: export PAGER less
You want
export PAGER=less
I do believe.
hamish (a tcsh user)
--
Hamish Moffatt Mobile: +61 412 011 176 [EMAIL PROTECTED]
Rising Software Australia Pty. Ltd.
Developers of music
hamish wrote:
On Mon, Mar 23, 1998 at 10:37:39AM +0100, E.L. Meijer (Eric) wrote:
in bask/ksh: export PAGER less
You want
export PAGER=less
I do believe.
Yep, moreover, I meant `bash' and not `bask'. Maybe Monday mornings
aren't the right time for emailing to the debian-user
Marcelo E. Magallón [EMAIL PROTECTED] writes:
[79 jacinta:~] while true ; do echo -n . ; /usr/sbin/update-alternatives
--display WindowMaker | grep -q 'WindowMaker-newstyle' ; done
.Broken pipe
From the grep man page:
-q, --quiet
Quiet; suppress normal output
I think that it is mostly historical (just about every Unix system since
about 1970 has had 'more').
There are some other reasons that are now at least mostly not
applicable. For example, 'more' will work on a printing terminal but I
believe that 'less' will not. There might be other VDTs that
On Sun, 22 Mar 1998 [EMAIL PROTECTED] wrote:
Some wonderful developer(s) fixed our manpage readers of
the coming release (hamm) so that they will also scroll upwards
to the beginning of any file we read. The manpages (accessed
by typing man nameofcommand--without the quotes) can
On Sun, 22 Mar 1998 [EMAIL PROTECTED] wrote:
[ snip ]
: (one newbie user who is looking forward to a new stable debian release that
: hopely won't include such obvious archiac software)
Hmm ... well, I hope it includes new _and_ archaic software ... some
of that stuff's quite useful! ;)
On Mon, 23 Mar 1998, E.L. Meijer (Eric) wrote:
[ snipped discussion of less vs. more ]
: Excellent comment, now let's go all the way and tell them newbie people
: how to _do_ it :)
:
: in bask/ksh: export PAGER less
: in csh/tcsh: setenv PAGER less
Excellent support :) BTW, these lines could
On Mon, 23 Mar 1998, Bill Leach wrote:
: I think that it is mostly historical (just about every Unix system since
: about 1970 has had 'more').
:
: There are some other reasons that are now at least mostly not
: applicable. For example, 'more' will work on a printing terminal but I
: believe
On Mon, 23 Mar 1998 09:27:21 -0600 (CST) [EMAIL PROTECTED] wrote:
One thing it will change is the behavior of 'make config' when
recompiling the kernel ... namely when you choose ``?'' to get more
information about that particular option. ``less'' will make you choose
``q'' to get back to the
On Mon, 23 Mar 1998, Bob Hilliard wrote:
: On Mon, 23 Mar 1998 09:27:21 -0600 (CST) [EMAIL PROTECTED] wrote:
: One thing it will change is the behavior of 'make config' when
: recompiling the kernel ... namely when you choose ``?'' to get more
: information about that particular option.
On Mon, Mar 23, 1998 at 09:38:53AM -0600, [EMAIL PROTECTED] wrote:
On Mon, 23 Mar 1998, Bill Leach wrote:
: I think that it is mostly historical (just about every Unix system since
: about 1970 has had 'more').
:
: There are some other reasons that are now at least mostly not
:
Has anyone gotten DOOM to work? Here, the program starts, but when I try to
move the cursor, or press any ke, after the Menu comes up the program stops
with the message 'broken pipe'. Any ideas?
Orn Einar Hansen
Orn E. Hansen wrote:
Has anyone gotten DOOM to work? Here, the program starts, but when I try to
move the cursor, or press any ke, after the Menu comes up the program stops
with the message 'broken pipe'. Any ideas?
What version of doom are you using? Do you have doom-musserver installed
Þann 01-Jan-98 skrifar Joey Hess:
What version of doom are you using? Do you have doom-musserver installed,
and if so, what version? Do you have a sound card?
The problem was, that I am using NAS to network'ize my soundcard, and that
meant doom couldn't acquire the card. Whenever I move
1 - 100 of 109 matches
Mail list logo
