Okay, running into a new problem suddenly. I thought I had seen this
problem on the list before - but my searches came up with nothing - so I
appologize if this is duplicated.
Now when I try to delete a user I get a segfault:
mail:/home/vpopmail/bin # vdeluser [EMAIL PROTECTED]
Segmentation fault
I did find one post about a month ago addressing a similar issue. The
author suggests to add an entry into the valias table:
adding a valias as this in the valias table:
alias domain valias_line
default foo.bar | /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox
and the vdeluser work correctly.
Which it did (but it did leave that alias in the table . . . not sure if
it should delete it or not - but I would imagine so).
I ran an strace on that and it does in fact segfault when examining the
valias table:
. . .
read(5, "# Default limits file. This fil"..., 4096) = 1161
read(5, "", 4096) = 0
close(5) = 0
munmap(0xb7f90000, 4096) = 0
fcntl64(4, F_SETFL, O_RDWR|O_NONBLOCK) = 0
read(4, 0x8061ea8, 8192) = -1 EAGAIN (Resource
temporarily unavailable)
fcntl64(4, F_SETFL, O_RDWR) = 0
write(4, "\1\0\0\0\16", 5) = 5
read(4, "\7\0\0\1\0\0\0\2\0\0\0", 16384) = 11
fcntl64(4, F_SETFL, O_RDWR|O_NONBLOCK) = 0
read(4, 0x8061ea8, 8192) = -1 EAGAIN (Resource
temporarily unavailable)
fcntl64(4, F_SETFL, O_RDWR) = 0
write(4, "P\0\0\0\3select valias_line from val"..., 84) = 84
read(4, "[EMAIL PROTECTED]"..., 16384) = 91
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
So, does any one have suggestions on how I can delete that?
. . .
crap. So I knew I saw this same problem somewhere else. It's noted in
the 5.4.22 changelog. Why oh why didn't I go with 5.4.22 ???
I'll post this anyways for posterity.
Matt
