http://bugzilla.lysator.liu.se/show_bug.cgi?id=877
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|inpro |
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=877
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=877
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
everconfirmed|0 |1
------- Additional Comments From ceder(a)lysator.liu.se 2003-01-10 01:59 -------
I have spent a few hours trying to reproduce this problem. As far as I can
tell, it cannot explain bug 212, since:
- mark-as-read can only be done by the person that is logged in
- the pers-stat of a logged-in person is locked in memory
- when a person logs out (using the "logout" request, using the
"disconnect" request, at server shutdown, or by disconnecting)
mark_person_as_changed() will be called before the pers-stat is
unlocked
However, this bug can cause the saved snapshot of the database
to be inconsistent, as demonstrated by bug-877.exp.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=877
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |inpro
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=563
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From ceder(a)lysator.liu.se 2003-01-08 08:49 -------
Thanks, Thorild. This appears to not break anything now. I don't know
if it works portably in IPv6 mode. If anybody who reads this runs an IPv6-only
host, it would be nice if you could set up a Xenofarm client for lyskom-server.
I'm closing this now. Any problems found with the IPv6 support should be
reported as new bugs.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=966
Summary: Supervisor of author not allowed to convert recipient
type
Product: lyskomd
Version: 2.0.7
Platform: All
OS/Version: All
Status: NEW
Severity: minor
Priority: P4
Component: server
AssignedTo: ceder(a)lysator.liu.se
ReportedBy: ceder(a)lysator.liu.se
QAContact: lyskomd-qa(a)lists.lysator.liu.se
Only the author of a text (and the supervisor of the recipient) is allowed to
convert the type of a recipient (e.g. from recpt to cc_recpt). The supervisor
of the author should also have this ability.
See FIXME in src/server/text.c.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=563
------- Additional Comments From thorild(a)Update.UU.SE 2003-01-06 21:32 -------
It seems that some OSes are picky about what address size you give as the third
arg to bind(). That third arg may, in isc_bindtcp(), be changed from
sizeof(ia->ip.saddr)
to
CHOOSE_IP4OR6(ia->ip.saddr,
sizeof(struct sockaddr_in),
sizeof(struct sockaddr_in6))
which seems to fix the problem.
This applies to isc_bindudp() as well.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=563
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |thorild(a)Update.UU.se
Keywords|inpro |
------- Additional Comments From ceder(a)lysator.liu.se 2003-01-06 15:04 -------
I'm considering backing out this patch. I don't want to spend a lot of
time debugging IPv6 support. Thorild, can you please figure out what
happens on Solaris 2.8 with your patch applied? Apparently, the bind()
call fails, but I don't know why.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=7
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Keywords|inpro |
Resolution| |FIXED
------- Additional Comments From ceder(a)lysator.liu.se 2003-01-06 14:13 -------
This is now implemented:
@node async-new-user-area
@section async-new-user-area (11) Recommended
@amindex async-new-user-area
@example
async-new-user-area [19] (( pers-no : @lt{Pers-No};
old-user-area : @lt{Text-No};
new-user-area : @lt{Text-No} ));
@end example
This message indicates that the user-area of @aarg{pers-no} has
changed from @aarg{old-user-area} to @aarg{new-user-area}. This
message is sent to all supervisors of @aarg{pers-no} (which of course
includes @aarg{pers-no} himself).
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=7
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |inpro
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.