August 2002 - openSUSE Programming - openSUSE Mailing Lists

Printing Problem (Cobol App)
by Stu Cater 29 Aug '02

29 Aug '02

I am a relative newbie at SuSE and I apologize beforehand if this is not the correct place for this questions. I have been asked to assist in moving an ACUCobol (Runtime is GT 5.1) application from SCO Unix to SuSE version 8.0. I've been able to get the program working, but can not get any of the reports to print. I am able to print from the command line and can successfully pipe a file to the printer (cat .profile | lp -s -dprinter). The COBOL config file defines the printer as: LPT1 -P lp -s -dprinter1 When I attempt to print from inside the program, I get a File Error 30,32. I had a programmer write a simple program to print a file, and that to results in the same error. This leads me to the conclusion that something in SuSE is not setup correctly (ACUCorp tech support indicates that many others are running Cobol Apps under SuSE), even thought I can print successfully. Thanks in advance for any assistance. Stu

3 3

Question on a kernel driver
by Libershteyn, Vladimir 25 Aug '02

25 Aug '02

Hi, All, I'm looking for a help on a kernel module programming issue. Currently I ran out of ideas why it does not work and I really appreciate any help. We have a hardware device I have a driver written for. It works without any problem on any of Red Hat versions with any version of kernel 2.4.x+ The same driver compiles fine on a SuSE 7.x enterprise, but here is a problem: For synchronization I use semaphores. Semaphores initializes with init_MUTEX_LOCKED function which basically set the atomic value of a count to 0. In a routine that looking for a data I use a function down_interruptible(&sem) which should check the count value to be 0 and if it so the thread goes to slip until the ISR will set the semaphore count back to initial value with a command up(&sem); What happens with my driver, when it comes to the command down_interruptible(...) the whole system just hangs. I could not find any restrictions on using this mechanism, but just for the testing I switched from using semaphores to wait queues. The result is exactly the same. What am I doing wrong? The kernel I'm running is 2.4.7-64G... and the OS is SuSE7.x Enterprise I did not try yet to run the same driver on a SuSE 8.0. I'll do it on Monday. Again, It works fine on any Red Hat OS Please help Regards, Vladimir Libershteyn HP, 408-285-5270

1 0

Socket Programming
by Nelson Ko 19 Aug '02

19 Aug '02

All, I am trying to use SuSE 8.0 for my socket programming project. I wrote a TCP socket server, with Perl (say on port 40180). I found that I couldn't telnet <hostname> 48010 to get connect to the TCP socket server. [... starting the socket server in background ...] > telnet deutsch 48010 Trying 127.0.0.2... telnet: connect to address 127.0.0.2: Connection refused Typing "netstat -a" doesn't show anything related to my socket server. Yet, I could load my program on a Solaris machine and get it running. Could anyone give me some hints? Is it the /etc/inetd.conf setting or some other configuration? Thanks in advance, nelson

2 1

kdevelop - new project cannot be created
by Setyo Nugroho 19 Aug '02

19 Aug '02

Hi all, Just installed kdevelop and qt-designer. Everything seems OK. Until I found this problem is: a new project cannot be created, i.e. pushing the "New" button from "File"-menu does not affect anything. Its colour is blurred. It seems this button is deactivated. FYI, I installed it in two modes: a. using yast2 b. using apt-get -f install kdevelop I use SuSE 8.0 installed. Any help would highly be appreciated. Regards, Setyo Nugroho

1 0

Frontpage 2002 Server Extensions
by Dan Jaksic 14 Aug '02

14 Aug '02

I just got done porting Microsoft Frontpage 2002 Server extensions to SuSE Linux 8.0 Professional and I thought I would post here so that others can benefit from my pains over the last two weeks. I am in the process of developing a website on my Linus box and I recently purchased Microsoft Frontpage 2002. To my great suprise I discovered that SuSE does not support Frontpage 2002 extensions (there is a frontpage 2000 (Version 4) package) and I was on my own to get the 2002 extensions working. To get things working, I needed patch my Apache server with a Frontpage patch which I got from www.rtr.com and the 2002 server extensions package from the same site. Once I downloaded both is when things got interesting. To make a long story short, here are some of the things I found in getting things to finally work: 1) File mod_frontpage.c seems to have a bug in its initialization code. It expects tha Apache server to call the FrontPageInit() function twice so the code does nothing on the first call and then does the Initialization on the second call. Well it just so happens that, at least for my configuration, the FrontPageInit function is called multiple times, but only once in a given process (while code thinks it will get called twice in the same process). Not good. So I modified my mod_frontpage.c code to fix this. 2) I kept getting IMAGESDIRbluedot.gif errors in my Apache error log so I searched through the Internet and I found a discussion thread that had the fix. Fix was to change IMAGESDIRbluedot.gif to IMAGESDIR/bluedot.gif in file Webadmin.css under the frontpage home directory tree. 3) I can't recall, but it seemed like I had to move around the "gif" files because they were in a different frontpage directory than was coded in the HTML logic 4) When I would access the Administrative website web server through Internet Explorer, the admin pages would appear OK, but when I tried to execute an admin command, I would get a standard browser download box asking me to download a file from the server. After a lot of digging, I discovered that the mime type passed by the Apache server was set to "application/x-msdos-program" when passing header information to the browser. It needed to be set to "octet-stream". The program frontpage uses is called "fpadmcgi.exe" on the server and this program dynamically creates the html response. To make a long story short I fixed the problem by changing my "mime.type" associated with the apache server. The ".exe" extension was associated with two mime types, "octet-stream" and the "application/x-msdos-program" so I just got rid of it for the x-msdos-program mime type so that the server was forced to use "octet-stream". But I think the real solution is to use the mime_magic module, but I did not want to spend the time so for now I just edited mime.types 5) The "fp_install.sh" script had some issues. For one, it always tries to install the stock (i.e prebuilt httpd version 1.3.19 apache executable even if you apply the Frontpage patch to a later version of the http daemon. Not good. In addition to that, it uses "strings -a" on your httpd executable to search for the keyword "FrontPage". But if you build the patch as a DSO module (i.e mod_frontpage.so), the "strings -a | grep FrontPage" command finds nothing and the script things you have not installed the Frontpage patch. Not good at all. 6) I ran into a problem where the script prompted me to create the admin server and it created it as a virtual server by updating the bottom of my http.conf file. It had a "Listen 2200" placed in the httpd.conf file when it defined the virtual server. It just so happened that that was the only "Listen" directive in my conf file. I had a "Port 80" directive in my file and I though I would get a server listening on the port 80 and on port 2200, but the listen overode the "Port 80{ directive and I only had one server listenning on port 2200. Bottom line is that I needed to put in a "Listen 80" directive once the script put in the "Listen 2200" directive. I hope this helps someone so that they don't waste as much time as I did getting this thing to work....

1 0