I did an experiment by building the libata drivers as modules. During
make modules_install, I got "Unresolved symbols" errors for every
driver. What kernel configuration option am I missing ?
depmod: *** Unresolved symbols in
/lib/modules/2.4.33.4-hardened-grsec/kernel/drivers/scsi/sata_nv.o
depm
Hi!
On Sun, Jun 17, 2007 at 04:39:59PM +0200, Adam Lantos wrote:
> a full recompile might be a good idea, but
>
> mysql,openldap & glibc-2.4 nptlonly worked well
> mysql,openldap & glibc-2.5 -nptl works well now
> mysql,openldap & glibc-2.5 nptlonly won't work
I don't use LDAP, but I'm using My
a full recompile might be a good idea, but
mysql,openldap & glibc-2.4 nptlonly worked well
mysql,openldap & glibc-2.5 -nptl works well now
mysql,openldap & glibc-2.5 nptlonly won't work
I have bdb,cyrus-sasl and openldap recompiled after every glibc merge.
So I think the issue is more glibc's n
I experienced problems while testing slapd and pam_ldap when I
originally updated to glibc-2.5* - hardened profile for me. Recompiles
fixed it.
BTW, I may be wrong in this ideology, but since gentoo is a from source
distro, in general I'd try recompiling dependencies of the offending
package
recompiling glibc-2.5-r3 (USE="-nptl -nptlonly hardened") and db,
openldap solved the issue.
On 6/17/07, Adam Lantos <[EMAIL PROTECTED]> wrote:
no, it wasn't me, and it wasn't PaX either. Kernel is
2.6.18-grsec-pax, and mysql and openldap worked well since half a
year... PaX works well, and log
no, it wasn't me, and it wasn't PaX either. Kernel is
2.6.18-grsec-pax, and mysql and openldap worked well since half a
year... PaX works well, and logs well when it kicks in.
another issue that could be related to this: sshd communication
processes die randomly. nothing there in syslog/kernel lo
On 16 Jun 2007 at 23:49, Adam Lantos wrote:
> [pid 11694] +++ killed by SIGKILL +++
if that SIGKILL wasn't you, it could have been PaX (if you're using it),
can you check your kernel logs for PaX messages?
--
[EMAIL PROTECTED] mailing list
