[SuSE Linux] two major question...
the first question is about firewalling SuSE 5.3, i've read the docs and found the example very usefull cause it's very similar to my conditions so i've setted up my policy like the docs show so the system seems to work (the other PCs can reach the internet) bu tat boot time when the service is started gives me an error on "... socket failed" i can't remember and in /var/log/* nothing talk about it. Can anyone explain me what does it means cause i don't matter about socket ? Second is for ISDN device, a Teles S0/16.3 passive card which at boot time is initialized correctly but al shutdown when the system try to unload the module give me an error on ... " cannot locate char-major-68 device... " after that it gives me some possibility that can have caused this error... like "kernel that does not support device major then 64... etc" Any hints is appreciated. Thanks Massimo Lusetti - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
I get that error from one of the netatalk modules on my current system, haven't had the chance to chase it down yet as serving for the powermac here isn't that high a priority yet... If you're not using netatalk you can turn it off rc.config.
the first question is about firewalling SuSE 5.3, i've read the docs and found the example very usefull cause it's very similar to my conditions so i've setted up my policy like the docs show so the system seems to work (the other PCs can reach the internet) bu tat boot time when the service is started gives me an error on "... socket failed" i can't remember and in /var/log/* nothing talk about it. Can anyone explain me what does it means cause i don't matter about socket ?
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Anybody on here have any luck booting Linux with an Adaptec 2920C (78xx). I've got one machine running with no problems with a 2940UW...but this cheaper "knockoff" version of the 2940 is giving me timeout errors with all of the SCSI boot disks. Any ideas? Rick Thompson Computer Resources Coordinator Motley + Associates, P.C. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
At 07:23 PM 12/1/98 -0500, you wrote:
Anybody on here have any luck booting Linux with an Adaptec 2920C (78xx). I've got one machine running with no problems with a 2940UW...but this cheaper "knockoff" version of the 2940 is giving me timeout errors with all of the SCSI boot disks.
Try recompiling the kernel and changing the timeout value under the SCSI driver section to a larger number. lunaslide * PGP key->pgpkeys.mit.edu port 11371 * * * * * * * ...the really profound changes in human life all have their ultimate origin in knowledge pursued for its own sake. * * * * * -Alfred North Whitehead * * * * * * * * - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Wed, 2 Dec 1998, Massimo Lusetti wrote:
the first question is about firewalling SuSE 5.3, i've read the docs and found the example very usefull cause it's very similar to my conditions so i've setted up my policy like the docs show so the system seems to work (the other PCs can reach the internet) bu tat boot time when the service is started gives me an error on "... socket failed" i can't remember and in /var/log/* nothing talk about it. Can anyone explain me what does it means cause i don't matter about socket ?
I had the same problem with 2.1.119 kernel. Compiling 2.0.34 fixed the problem. I do not know what the deal is... Not sure about your second major question. -alexm - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, my /var/log/messages stopped being updated... any pointers? -alexm - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
alexm wrote:
Hi,
my /var/log/messages stopped being updated... any pointers?
Look in your /var/log/boot.msg and see if your klogd has started. If not try to trace down where it isn't getting started. You may have turned off logging in the system configuration file in Yast. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
killall -HUP syslogd alexm wrote:
Hi,
my /var/log/messages stopped being updated... any pointers?
-alexm
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- ------------------------------------------------ Tony Halsell, Hewlett Packard HPSD ITRC Staff thalsell@rsn.hp.com ------------------------------------------------ UNIX is user friendly. It's just selective about who its friends are. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hallo, Thanks to everyone who responded. Restarting the syslogd did the trick :-) On Wed, 2 Dec 1998, Tony Halsell wrote:
killall -HUP syslogd
alexm wrote:
my /var/log/messages stopped being updated... any pointers?
BTW, can anyone tell why some daemons keep dying after certain amout of time? My system has been running since May. During that time I had to manually restart inetd (twice), sendmail (once), syslogd (once). Also, I can not log in on TTY1 anymore... It displays: login: If I start typing it echoes the characters, but when I press "ENTER" it displays ^M and does not give the "passwd:" prompt. I know a reboot can cure this -- it happened before, but I'd rather not to reboot. Also, all other ttys run as /sbin/mingetty tty# but on tty1 it runs as /sbin/mingetty --noclear tty1 ^^^^^^^^^ Killing the process does not help --> it respawns with a different PID but with the same --noclear option and nothing works again. Any info is greatly appreciated. Sorry for a long post. -alexm - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
ctrl m will should give you a return key if not your mapping of your keys has changed for the screen. On Wed, 2 Dec 1998, alexm wrote:
Hallo,
Thanks to everyone who responded. Restarting the syslogd did the trick :-)
On Wed, 2 Dec 1998, Tony Halsell wrote:
killall -HUP syslogd
alexm wrote:
my /var/log/messages stopped being updated... any pointers?
BTW, can anyone tell why some daemons keep dying after certain amout of time? My system has been running since May. During that time I had to manually restart inetd (twice), sendmail (once), syslogd (once).
Also, I can not log in on TTY1 anymore... It displays: login: If I start typing it echoes the characters, but when I press "ENTER" it displays ^M and does not give the "passwd:" prompt. I know a reboot can cure this -- it happened before, but I'd rather not to reboot. Also, all other ttys run as /sbin/mingetty tty# but on tty1 it runs as /sbin/mingetty --noclear tty1 ^^^^^^^^^ Killing the process does not help --> it respawns with a different PID but with the same --noclear option and nothing works again.
Any info is greatly appreciated. Sorry for a long post.
-alexm
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
participants (8)
-
alexm＠htr-60.tx.symbio.net -
charlesiii＠theverge.com -
lunaslide＠pacbell.net -
m.lusetti＠mo.nettuno.it -
rthompson＠motleypc.com -
thalsell＠rsn.hp.com -
wizard01＠impop.bellatlantic.net -
zentara＠mindspring.com