Shutdown messages not visible after xdm stopped
Hi, I recently set up a hamm-system running xdm. When shutting down, there are no messages from the moment xdm disappears and the console comes back until to the final system halted. I disabled xdm and used startx. After beeing back from X to the console I noticed that all messages during shutdown are issued. Anyone else ? Kind regards Gerd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to configure sendmail for dial on demand operation ?
Torsten Hilbrich writes: Gerd Bavendiek schrieb am Sun, 31 May 1998 17:24:30 +0200 (CEST): Hi, My box is connected to my ISP via an ISDN router (Ascend pipeline), which does dial on demand. I don't want sendmail to establish connections in the background. The mail processing shall be delayed until I explicitly make a connection. If you don't need to receive mail via smtp, just remove sendmail from the inetd.conf or the /etc/rd.*d/ directories. Assuming, that it is started using the SysV init scripts, just issue the following command: update-rc.d -f sendmail remove to prevent its invocation on next startup. (BTW: Is there a way for doing this that will survive the next sendmail update?) I do need a running sendmail. Thanks to Cleto Pescia [EMAIL PROTECTED] who pointed me to http://oliva.home.ml.org/diald-win-e.html I got a running configuration. Kind regards Gerd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
How to configure sendmail for dial on demand operation ?
Hi, My box is connected to my ISP via an ISDN router (Ascend pipeline), which does dial on demand. I don't want sendmail to establish connections in the background. The mail processing shall be delayed until I explicitly make a connection. Though I found various hints on I was not able to make it work for me. I'm using the Debian sendmail-package 8.8.8-16. This is my current customization section in sendmail.mc: ## Custom configurations below (will be preserved) define(`confDELIVERY_MODE', `delay') FEATURE(nodns)dnl FEATURE(nocanonify)dnl FEATURE(nouucp)dnl FEATURE(masquerade_envelope)dnl define(`SMART_HOST', `relay:[rw.sni.de]')dnl define(`confCON_EXPENSIVE', `True')dnl MASQUERADE_AS(rw.sni.de)dnl define(`confUSERDB_SPEC', `/etc/mail/userdb.db')dnl FEATURE(notsticky)dnl MAILER(local)dnl MAILER(smtp)dnl There is no nameserver on my box. Any hints really appreciated ! Kind regards Gerd -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
plip connection to laptop breaks after laptop disk powers down
Hi, recently I connected my laptop B via PLIP to my Tower A at home. Both are running Debian 1.2 (Kernel 2.0.27). Everything works wells as long as the laptop's disk is busy. After 120 sec been idle the disk is run down. This is the moment when the connection between Tower and laptop seems to be down. To be precise: - on tower A I can no longer ping, rlogin etc. to laptop B - using B, I CAN PING A - after that I can again reach B from A - for another 120 sec Of course I get plip-driver messages on A like these: Jun 20 09:47:40 nana kernel: plip1: receive timeout(2,c7) As long as the line is busy, everything works quite well. My throughput is about 38 kB/sec. My plip is Jun 20 06:04:09 nana kernel: NET3 PLIP version 2.2 [EMAIL PROTECTED] Jun 20 06:04:09 nana kernel: plip1: Parallel port at 0x378, using assigned IRQ 7. Any hints ? Kind regards Gerd -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
lpr: connect: No such file or directory
Hi,
I just tried to install another network printer. After fiddling with
/etc/printcap I got problems. To make a longer story short: I decided
to dpkg -r lpr. This went fine. So I reinstalled lpr, using
lpr_5.9-12.deb.
After setting up rm and rp in /etc/printcap I tried lpr ...
This is what I got (doing this as root):
zaza:/mnt lpr /etc/passwd
lpr: connect: No such file or directory
jobs queued, but cannot start daemon.
Stracing this command gave me:
888 link(/var/spool/lpd/lp/tfA001Aa00888, /var/spool/lpd/lp/cfA001Aa00888$
888 unlink(/var/spool/lpd/lp/tfA001Aa00888) = 0
888 socket(PF_UNIX, SOCK_STREAM, 0) = 4
888 connect(4, {sun_family=AF_UNIX, sun_path=/dev/printer}, 14) = -1 ENOENT$
888 fstat(1, {st_mode=S_IFCHR|0622, st_rdev=makedev(4, 198), ...}) = 0
888 mmap(0, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0$
888 ioctl(1, TCGETS, {B38400 opost isig icanon echo ...}) = 0
888 write(1, lpr: connect: No such file or di..., 40) = 40
888 close(4) = 0
888 write(1, jobs queued, but cannot start da..., 38) = 38
888 _exit(0) = ?
Of course strace was right: There was no /dev/printer.
After rebooting without ANY CHANGES to /etc/printcap etc. :
zaza:/var/spool/lpd/remote ll /dev/pr*
19075 srwxrwxrwx 1 root root0 Mar 18 11:44 /dev/printer
Printing worked fine again.
What happened ? Any hints ?
I saw the very same question searching http://www.dejanews.com but
unfortunately without any answer.
Someone any hints ?
Gerd
PS/2 Mouse Driver in Debian 1.1 2.0.0
Hi, I just installed Debian 1.1 on a system with a PS/2 Mouse. Unfortunately I'm missing /lib/modules/2.0.0/misc/psaux.o. There is a descriptive file in /usr/lib/module-help/modules/psaux. Additionally I took kernel-image-2.0.0-0.deb and kernel-image-2.0.6_2.0.6-0.deb. But there is no psaux.o in this packages - so I can't use my mouse :-( Maybe it has been asked before - but I have been away for months. Any hints ? Gerd
Socket destroy delayed (r=0 w=1340)
Hi, on a quite recently installed Debian-1.1 box I sometimes encounter the following. koko:/root ping us1by-6 PING us1by-6 (156.53.107.26): 56 data bytes --- us1by-6 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss Socket destroy delayed (r=0 w=1340) || I never saw this before ! Anything to worry about ? My netbase is version 2.02-1. Gerd
ftp+rcp: Connection refused
Hi, I just installed a Debian 1.1 System using latest packages. Everything went fine, but one problem remains: I can ftp TO the new system. I cannot ftp FROM my new system, named koko. So being on koko and doing: ftp zaza gives me: ftp: connect: Connection refused strace gives me: ipc_subcall ... ERRNO 111 Connection refused Similar goes for rcp. koko is part of a LAN. Most of the packages I could install by mounting a NFS-Filesystem. I'm afraid, solution might be obvious, but right now I have no idea. Any help apreciated ... Gerd
