Hi everyone,

I have set up and have a fully functional qmail 1.05. I am now attempting to patch this and have only been successful half way. Specifically, I have done the following:

1) Copied the C script code for Russell Nelson 'percenthack' patch and placed it into a file called PercentPatch.c

2) I successfully applied the patch to the qmail-smtpd file in the source tree.

3) I stopped qmail using qmailctl stop (configured this when using the Life with Qmail how to)

4) Then I issued: make setup check

This is were I got an error: '

install: fatal: unable to write ..../bin/qmail-lspawn: text busy
make: *** [setup] Error 111

5) After I received this it seemed as if the qmailctl stop didn't stop all the processes required by qmail so I went to the KDE system gaurd and killed all the processes relative to qmail. I tried the 'make setup check' and again received the same error.

Can you please provide suggestions on how I might get qmail-lspawn text NOT busy, it would be appreciated.

Thank you,
ServerStorm

I am wondering if you by any chance found a solution to this problem by now. I am experiencing the same problem in attempting to install qmail. I'm going to keep on trying to find a solution to this problem, if i find it I will post it in case you still need it. If You have it I would be much obliged to find out how.

Thanks

Hi Cerebral.

I did two things to get past this:

1) I used instructions other than "Life with Qmail" - great instructions only they didn't work on my configuration of SuSE very well. Instead I used the following

2) I made sure that I was in the appropriate directory when applying the patch. In my case, I needed to go the the directory where I had un-tarred the source files and apply the patch there. This source directory is not to be confused with the 'SRC' folder that has all the C files designated by filename.h; rather, you need to be in the folder where you un-tarred your original qmail files (or whatever files you are attempting to patch.)

Hope this helps or that you alread have found a solution.

Truly,
ServerStorm