SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
today there was an upgrade to openssl which breaks functioning of proftpd. From my /var/log/syslog:
Code:
Jul 29 12:35:39 dakini proftpd[3327]: mod_tls/2.1.2: compiled using OpenSSL version 'OpenSSL 0.9.8g 19 Oct 2007' headers, but linked to OpenSSL version 'OpenSSL 0.9.8h 28 May 2008' library
Jul 29 12:35:39 dakini proftpd[3327]: Fatal: unable to load module 'mod_tls.c': Operation not permitted
"Ok", I thought, "I'm going to recompile proftpd to link it against the new includes". So I fetched the source directory from ftp.slackware.com and started ./proftpd.Slackbuild. But - to my surprise - it failed to compile:
Code:
config.status: creating Makefile
config.status: creating Make.rules
config.status: creating config.h
config.status: executing default commands
echo \#define BUILD_STAMP \"`date`\" >include/buildstamp.h
cd lib/ && make lib
make[1]: Entering directory `/tmp/proftpd-1.3.1/lib'
ccache gcc -DHAVE_CONFIG_H -DLINUX -I.. -I../include -O2 -march=i486 -mtune=i686 -Wall -c pr_fnmatch.c
In file included from /usr/include/asm/sigcontext.h:6,
from /usr/include/bits/sigcontext.h:29,
from /usr/include/signal.h:334,
from /usr/include/sys/wait.h:32,
from ../include/conf.h:96,
from pr_fnmatch.c:39:
/usr/include/asm/types.h:6: error: conflicting types for ‘mode_t’
/usr/include/sys/types.h:72: error: previous declaration of ‘mode_t’ was here
make[1]: *** [pr_fnmatch.o] Error 1
make[1]: Leaving directory `/tmp/proftpd-1.3.1/lib'
make: *** [lib] Error 2
So, does someone has got an idea what to do to get a working proftpd again?
The installed kernel headers on my box are kernel-headers-2.6.24.5_smp-x86-2 which matches the installed kernel source and the running kernel.
Try changing this:
--with-modules=mod_readme:mod_ratio:mod_tls:mod_wrap:mod_ctrls_admin
to this:
--with-modules=mod_readme:mod_ratio:mod_wrap:mod_ctrls_admin
You my have found a bug in the sources. I see that version 1.3.2rc1 is out, so you might as well try compiling the very latest: http://proftp.oslevel.de/
If none of that works, try simply re-compiling the same old version you were using before. These errros with sys/types.h are pretty common, but the fact that it mentions mode_t seems to indicate improperly written includes vis-a-vis newer glibc versions- mode_t has to be handled differently for 64bit compatibility
I'd like to comment that you should consider maybe switching from proftpd to vsftpd. It's secure, stable and seems to have a better track record from proftpd.
I'm posting here to let everyone know that we're taking fast action. ProFTPD 1.3.1 packages are tested and uploading now. Once checksums are verified they'll be out on OSUOSL first. I expect that will be within the hour.
Also, vsftpd is my personal choice when I'm running an FTP server (I trust Chris Evans when it comes to security matters), but if I'm not mistaken ProFTPD does have some desirable features that are absent in vsftpd, so it's good to have choices.
Also, vsftpd is my personal choice when I'm running an FTP server (I trust Chris Evans when it comes to security matters), but if I'm not mistaken ProFTPD does have some desirable features that are absent in vsftpd, so it's good to have choices.
Yes, choices are good. It's nice that both are available in Slackware for such reasons.
So when are you going to start including postfix in Slackware alongside sendmail...
OK, the new ProFTPD packages are out on ftp.osuosl.org. Please let me know if there are problems with them, or any other issues related to the recent updates.
As far as Postfix -- we keep talking about it, but it's hard to know where to draw that line. There's already a build script for it on slackkbuilds.org, and we're trying to keep from adding _everything_ to the main Slackware tree, as we generally end up looking at continual "inflation" anyway.
That said, it's been something on the table for quite some time now...
Another OpenSSL upgrade, and proftpd died in the same way. The new patch did not recognise all the directives in the configuration file:
$$tail proftpd.log
Mar 15 19:42:56 biolpc22 proftpd[5963]: Fatal: unknown configuration directive 'DisplayFirstChdir' on line 57 of '/etc/proftpd.conf'. Is commenting the line 57 enough?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.