August 2001 - openSUSE Users - openSUSE Mailing Lists

Re: [SLE] LILO + SuSE 7.2 on SCSI-Drive
by Alexandr Malusek 01 Aug '01

01 Aug '01

Vincent Allard <v.allard(a)easynet.be> writes: > Situation: when i start my PC, LILO presents to me the choice of kernel to > start ==> OK > BUT when i restart my PC without doing a physicaly shutdown, LILO starts > without proposed me choices. I suspect that it's not normal. I think it's a feature. If you restart from KDM, then lilo uses its -R option to select the next OS to boot. It modifies the lilo behavior, see man lilo. -- A.M.

3 2

Quick way to forward all the messages in a spool to a remote address
by wilson＠claborn.net 01 Aug '01

01 Aug '01

Hello, I'm having a situation where I need to forward the last mails in someone's spool dir to anthoer address. Please note that I'm using Postfix for my MTA. I tried the following: cat /var/spool/virtual/domain.tld/jw | sendmail jw(a)claborn.net But that sends the whole file as one enormous message. I need it to read the spool and break it up into messages. Any ideas? I have several spools to do this to, so I cannot do it by hand. TIA! ---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com Central Texas IT http://www.centraltexasit.com

2 1

RE: [SLE] Email Settings?
by Watson, Randy 01 Aug '01

01 Aug '01

The message that Jeff sent came through, but, no others. Here is the log file for the message received. Aug 1 15:47:27 yucca postfix/smtpd[4173]: connect from cs279-229.austin.rr.com[24.27.9.229] Aug 1 15:47:28 yucca postfix/smtpd[4173]: 6CC406392C: client=cs279-229.austin.rr.com[24.27.9.229] Aug 1 15:47:28 yucca postfix/cleanup[4176]: 6CC406392C: message-id=<20010801111722.F8198(a)elendil.bearhouse.lan> Aug 1 15:47:28 yucca postfix/qmgr[418]: 6CC406392C: from=<jeff.taylor(a)ieee.org>, size=815, nrcpt=1 (queue active) Aug 1 15:47:28 yucca postfix/smtpd[4173]: disconnect from cs279-229.austin.rr.com[24.27.9.229] Aug 1 15:47:28 yucca postfix/pipe[4192]: 6CC406392C: to=<rwatson(a)turbowarp.net>, relay=procmail, delay=0, status=sent (yucca.turbow -----Original Message----- From: Jeffrey Taylor [mailto:jeff.taylor@ieee.org] Sent: Wednesday, August 01, 2001 12:20 PM To: Watson, Randy Subject: Re: [SLE] Email Settings? Done, Message ID: 6CC406392C Jeffrey Quoting Watson, Randy <rwatson(a)OFDA.NET>: > Jeff, > > Thanks, I see your message in the logs, but it is to the postmaster account. > User account still can't receive mail from outside. > > Try rwatson(a)turbowarp.net > > Thanks > Randy > > From: Jeffrey Taylor [mailto:jeff.taylor@ieee.org] > Sent: Wednesday, August 01, 2001 9:59 AM > To: suse-linux-e(a)suse.com > Subject: Re: [SLE] Email Settings? > > > /var/log/maillog or something similar. Depends on how your > syslog.conf is set up. I just sent mail to the postmaster and it was > accepted (Message ID 4661A6392C). I am not using SuSE Email Server > II, but I am using Postfix the Mail Transfer Agent (MTA) in it. > > HTH, > Jeffrey > > Quoting Watson, Randy <rwatson(a)OFDA.NET>: > > Hello all, > > > > Just installed SuSE Email Server II, simple install, one domain. Set MX > to > > server yucca.turbowarp.net. Users can send mail from yucca, but cannot > > recieve mail from outside. > > > > Users on yucca, can send/receive to each other, but not receive from > > outside. > > > > Where do I start looking? > > > > Thanks > > Randy > > > > > -- I don't do Windows and I don't come to work before nine. -- Johnny Paycheck

2 1

php/apache question
by Seth Payne 01 Aug '01

01 Aug '01

Hello, I have written some PHP code and am trying to execute it on my SuSE server but I get this message: Method Not Allowed The requested method POST is not allowed for the URL /do_showfielddef.php3 Does anyone know what I have to configure to allow the POST method? Seth R. Payne 2NetFX Field Sales Engineer 801.932.6406

1 0

[SuSE PEOPLE] Is 'less' broken in 7.2?
by Ted.Harding＠nessie.mcc.ac.uk 01 Aug '01

01 Aug '01

[SuSE FOLK PLEASE READ, especially at the end] ... Well, actually, no, 'less' isn't broken; but I thought it migfht be until I sussed it out. Having done that, I'm just irritated. On several text files, I have had the experience that less filename e.g. less /usr/share/groff/tmac/tmac.s just gives me a blank screen with, at the bottom, /usr/share/groff/tmac/tmac.s lines ?-?/? (END) as if it had read an empty file. On the other hand, if you open that file in 'vim' (or any of the others I've had this trouble with) you can see that it's well populated and a totally normal text file. (As one of the groff maintainers, I was about to give you a blasting for sending out 'groff' with empty 'tmac' files; but I thought I'd better root around before doing that). Well, it turns out that there's a 'less' preprocessor, /usr/bin/lessopen.sh, which examines the file and possibly does things to it before handing it over to 'less', using 'file' to determine the type. Of course, something like that has been the case for a long time, and it's handy for zipped text files and like binary- looking stuff. But now, after testing for binary-type stuff such as gzip, Zip, compress, bzip, etc., it then moves on to - groff source - tar archive - RPM - DVI, PS, PDF, HTML, Debian archive and proceeds to run, respectively, 'groff' (in sundry variations), 'tar -tvvf', 'rpm -qip' then 'rpm -qlp', dvi2tty, 'ps2ascii', 'pdftotext', 'lynx', 'dpkg-deb' or 'nm'; then it send the output to 'less. Which is, of course, why nothing happened when I used less on tmac.s -- 'file' recognises this as groff source and runs groff on it. But, of course, it being a macro file, this will produce no output from groff. Which is where this story started. ================================== The point I want to make, SuSE, folks, is that this behaviour of 'less' is overkill. Of course you can work round it by 'cat file | less' or 'less < file', which looks simple enough. But there's s point of principle here. Historically, in the GNU environment, 'less' has been the preferred tool of people scanning text files, preferable to 'more' because you can go back as well as forward. A classic example of "a tool which does one job, and does it well". But now, thanks to the admittedly valiant efforts of Vladimir Linek (who seems to have prepared lessopen.sh specially for SuSE), we now have something which is is trying to be a "universal" file reader -- groff, DVI, PS, PDF, HTML, whatever, 'less' will mangle it with something that has some capability for that file type. Note that many of the preprocessing programs are not the most suitable and will fail for a lot of files of the respecive type. Even 'ps2ascii' will make an absolutely lousy job on many PS files which, properly, would display as pure text. (I have a straight- forward .ps file with 17 columns of plaintext data on 1151 lines, 44978 non-space ASCII characters, for which ps2ascii gives me 235 non-space ASCII characters on 84 lines). So we now have 'new less' which tries to do many different jobs and may well do any one of them very badly (such as displaying /usr/share/groff/tmac/tmac.s ). At least, in say KDE, if you click on a file in the file manager it will normally open it with something that does a proper job (though of course it can occasionally get that wrong too). But even here I'm somewhat against the practice, because it associates ONE particular application with any particular file type, and there can be all sorts of reasons why you may want to process the file with something else (if a groff source file, then not only 'groff', but 'vim' for editing it, or -- yes -- even 'less' for scanning it). Nevertheless, so longas the filetype/application association does not become too invasive, it has its uses; and the fact that it only happens in KDE when you click in the file manager means that you can rattle away on your command line as you please, and know what you're going to be getting. But what has happened with 'less' is, I think, indeed too invasive. Unless you edit whatever it is (and hands up everyone who DOESN'T know whatever it is) that sets your $LESSOPEN EnvVar whenever you log in, or unset it yourself whenever you log in, or edit lessopen.sh to cut out everything you don't want and keep what you will find useful and not intrusive, then you will find that 'less' takes over and does what_it_thinks_you_need without using any sort of "intelligence" to determine what_you_want. And if this reminds you of another operating system (whose behaviour in this respect has at times literally had me breaking things) then I'm in your company. I would not like to see what has been a very sound Linux distribution, and reasonably flexible to handle and control, go down the road of "knowing better than the user" (and, by the way, doing a bad job of "knowing better"). Of course, as I say, having sussed it out I now know I can work round it with 'less < file' or the like. But I shouldn't have to because of the reasons given above, for in my mind these are bad reasons. If somebody wants to comsult an HTML document using lynx and view the result with 'less' then let THEM do 'lynx -dump filename | less' (or any other HTML interpreter if they so wish); If I need to scan the HTML code, I want to be able to do 'less filename' and get what I expect, not have to track down some file or other which happens to be /usr/bin/lessopen.sh in order to find out why I didn't get it. SO SuSE FOLKS, Please come back off this road you're going down. ============== If you want an all-singing (even if out of tune) all dancing (even if falling over too often) "less" with all that gizmo in lessopen.sh, then give it a different name (even "LESS"), so that we can avoid it unless we want it, and restore our friendly useful tool which may only do one job but does it bloody well. And the same for any other tools which may be going down the same road. And, finally, if your response to the above is "Since you clearly know how to deal with it, you can sort it out it yourself", my answer will be "Yes, I do; and I intend to. But I damn well want you to know why I'm doing that. If only for the sake of other people." Thanks for getting this far. And please take this seriously: I've been in this game too long for the above to be an ill-considered rant. It is, rather, a protest against indications of an imminent dumbing down [and why would anyone want to do that ... ?] of an operating system that really only works properly when it is understood (at any rate up to a certain level) but then works spendidly. SuSE, with 7.2, seems to be getting to the point where I can only use it properly if I start undoing stuff which SuSE have done, in order to restore some of the native simplicity and transparancy of Unix. I do not want, and indeed resent, anything which excessively intrudes on using the system as I want. It's like driving a car which suddenly says "I'm going to turn left here" or "here we stop for a picnic", and it then takes me all afternoon fiddling with its settings to get it to change its mind since I have a journey to finish. If (as of course there isn't) there was any "intelligent intent" behind the behaviour of 'less' with the above tmac.s file, it could only be interpreted as "This user is trying to read a groff macro file. He doesn't need to do that, nor know what's inside it, and probably he'd better not in case he does something he shouldn't." Well, there _are_ systems that behave like that; and I avoid them as far as possible. Best wishes to all, Ted. -------------------------------------------------------------------- E-Mail: (Ted Harding) <Ted.Harding(a)nessie.mcc.ac.uk> Fax-to-email: +44 (0)870 167 1972 Date: 01-Aug-01 Time: 17:04:03 ------------------------------ XFMail ------------------------------

1 0

RE: [SLE] Email Settings?
by Watson, Randy 01 Aug '01

01 Aug '01

Jeff, Thanks, I see your message in the logs, but it is to the postmaster account. User account still can't receive mail from outside. Try rwatson(a)turbowarp.net Thanks Randy -----Original Message----- From: Jeffrey Taylor [mailto:jeff.taylor@ieee.org] Sent: Wednesday, August 01, 2001 9:59 AM To: suse-linux-e(a)suse.com Subject: Re: [SLE] Email Settings? /var/log/maillog or something similar. Depends on how your syslog.conf is set up. I just sent mail to the postmaster and it was accepted (Message ID 4661A6392C). I am not using SuSE Email Server II, but I am using Postfix the Mail Transfer Agent (MTA) in it. HTH, Jeffrey Quoting Watson, Randy <rwatson(a)OFDA.NET>: > Hello all, > > Just installed SuSE Email Server II, simple install, one domain. Set MX to > server yucca.turbowarp.net. Users can send mail from yucca, but cannot > recieve mail from outside. > > Users on yucca, can send/receive to each other, but not receive from > outside. > > Where do I start looking? > > Thanks > Randy > > -- I don't do Windows and I don't come to work before nine. -- Johnny Paycheck -- To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com For additional commands send e-mail to suse-linux-e-help(a)suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com

1 0

RE: [SLE] Unexpected IRQ trap
by Iain Gray 01 Aug '01

01 Aug '01

doesnt seem to do much, apart from make the connection die with no error message when i place a load on it! what does unexpected IRQ trap actually mean? Could it be a hardware conflict? thanks, Iain > -----Original Message----- > From: root [mailto:root]On Behalf Of Jaakko Tamminen > Sent: 01 August 2001 11:55 > To: Iain Gray > Subject: Re: [SLE] Unexpected IRQ trap > > > Hello > > I would try the following in smb.conf: > max xmit = 8192 > > It sets the limit of the packet size transmitted, and could help Your > case, if there is some issue with the LAN and P120 speed. > > J. Tamminen > > > Iain Gray wrote: > > > Hello, > > > > i have recently set an old P120 of mine as a samba server, with > > an AMI Raid card and a Kingston KNE120 TX network card. This all > > works okay, except when I try to copy a large amount of files to > > or from the server, i get an "kernel : unexpected IRQ trap at > > vector 5f", and the machine loses network connectivity and has to > > be rebooted. I'd like to sort this out, but i have no idea where > > to start, as the usual sources seem to have very little info! > > > > Thanks, > > > > Iain > > > > -- > > To unsubscribe send e-mail to suse-linux-e-unsubscribe(a)suse.com > > For additional commands send e-mail to suse-linux-e-help(a)suse.com > > Also check the FAQ at http://www.suse.com/support/faq and the > > archives at http://lists.suse.com > >

1 0

Bad behaving software PIXEDIT
by Jaakko Tamminen 01 Aug '01

01 Aug '01

Hello Be warned... I ran "pixedit", then it wanted me to pick a windows to edit the pixel. No matter what I clicked, it did not accept that... Okay, that is understandable. But then I wanted to stop pixedit.. No way! There just was not means to "get out of" it.. I could not switch to another screen, terminal, nothing. The only solution that I found was to go to my SuSE router box, log in there, SSH from there back to my workstation, and kill that process.. ...stupid software... J. Tamminen

2 2

Re: [SLE] Adding a scsi-disk to Linux
by David List 01 Aug '01

01 Aug '01

On Sunday 29 July 2001 19:23, Bruce Marshall wrote: > All of the above tells me this is a hardware problem. How about > termination? The controller has internal termination, and from there a high quality LVD cable runs to the two drives. I am using the same active LVD/SE terminator after the drives that I used with only one drive. I have tried with and without termpower supply from the second drive. > What scsi controller are you using? (not that it should really matter) The controller is an onboard dual-channel sym53c1010 using the driver sym53c8xx. The two Ultra160 channels are completely separated, so that one can run Ultra160 on one and have single-ended devices on the other. The drives that I use are IBM 36LZX 18.3 GB Ultra160. After the last installation I have ID7 on the controller, ID0 on the installed drive and ID2 on the drive that I cannot get attached. That way, the second drive should appear as /dev/sdb and the installed drive still be /dev/sda if I ever succeed in getting the second drive attached to a running system. Oh, and I have a DVD-ROM drive on the other bus. I have tried disconnecting that, but to no avail. > Does the controller show you the two drives (and their ID's) at boot up? Yes, the drives are both visible from the controllers ROM configuration tool, and I can low-level format and verify both of them. > Assuming you can only use one drive, would either one of them have worked > for your re-install? (that is, by themselves, they both work fine?) Yes, the new installation has been made on the new drive and the old drive, which also worked, is now low-level formatted and unattached to the bus. Best regards, David List

4 9

printer woes
by dep 01 Aug '01

01 Aug '01

greets. a couple of thorny printer issues here. first is an epson stylus photo 780, which seemed to set up uneventfully using yast2 and cups. prints test pages fine, even at 720x1440 (there being no driver supporting its 2880x720 mode). i was even able to save the configuration. but when printing photos in high-res from the gimp, the first half of the page prints and then -- it stops. this is troubling and expensive -- this photo paper is a buck a pop! anyone encounter/solve this? there is no exact driver, but the stylus photo 750 driver in cups is said to work. linuxprinting.org says that this printer works perfectly under linux, but provides no details as to how to bring it about. the support database says nothing on the subject that i can find. and of course epson officially has never heard of linux. second issue: i'm trying to make use of my laserjet III-D as a network printer via its jet direct card. h-p has its administrative software for download (and i've downloaded it) but it's said to be for rh-5.2/suse-6.4, and i'm by no means certain it's gonna work with 7.2, which is what i'm running. printer and jet direct card are old, as in 10 years old. anyone experienced in this stuff? thanks! -- dep one day, you'll wish it was now. your wish has been granted. don't waste it.

1 0