 Oswald Buddenhagen
|
a1c402678c
split driver->prepare into ->prepare_opts and ->prepare_paths
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
4e983506d3
#include limits.h (for INT_MAX)
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
1a6ee00d86
less confusing uid ranges in debug
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
d414d0aae2
solaris 10 fix: use sys/filio.h for FIONREAD. untested.
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
8b6ac97fe4
adjust to: omit flags other than "deleted" when expunging target.
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
3c8ee66bfc
collect stderr as well.
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
f6ed69a8d3
don't record we synced flags if we didn't.
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
2fa54425e7
have to flush debug as well ...
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
76de0182a2
of course F_DELETED will have been added to expired slave messages, so
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
8c30ec4a25
put message references into the sync records. match up the uids after
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
61dfbea617
"reformat" S_EXP_S setting logic for understandability.
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
808001c0a9
whoops
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
4ec56f8cf6
- instead of having {m,s}foo, we have foo[2] now, so we can do
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
f070f3cd72
show debug output on error.
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
d68dd7369e
make the error case output more useful by dumping the entire data set.
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
549c1cf13e
fix error message
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
716ff82540
add expiration tests
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
ad5f5aa2b2
add MaxSize tests
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
ab898f2f5c
when dumping mailboxes, sort by uid 1st.
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
d3faf0d27f
detect excess messages after sync
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
924e1a7f04
sync state reader:
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
963f607c81
don't eat array lead-in on empty arrays
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
4dc23fee7b
why would somebody manipulate an expired message? right, he wouldn't:
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
9740e7e852
message tweaks
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
d5a1f5876d
more logical order
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
044d8dfb73
add some regression testing.
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
5633236ed2
fix sync entries not being purged due to c&p error.
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
8db5ec1e5e
less confusing error message on invalid mailbox.
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
6d229848a5
it's beyond me what this memset was supposed to do ...
|
%!s(int64=19) %!d(string=hai) anos |
|
Oswald Buddenhagen
|
633869d040
trailing whitespace
|
%!s(int64=19) %!d(string=hai) anos |
