Subject: [Bug 171] Core dump while starting the server for the first time - msg#00067

List: cms.citadel.devel

Date: Prev Next Index Thread: Prev Next Index

http://bugzilla.citadel.org/show_bug.cgi?id=171

*** shadow/171 Wed Dec 14 16:54:34 2005
--- shadow/171.tmp.16097 Thu Dec 15 23:28:59 2005
***************
*** 3,10 ****
Version: 6.x
Platform: PC
OS/Version: NetBSD
! Status: NEW
! Resolution:
Severity: major
Priority: P2
Component: server
--- 3,10 ----
Version: 6.x
Platform: PC
OS/Version: NetBSD
! Status: RESOLVED
! Resolution: FIXED
Severity: major
Priority: P2
Component: server
***************
*** 36,38 ****
--- 36,49 ----
ok to add begin_critical section in that function.

Please comment.
+
+ ------- Additional Comments From
ajc-1dPMbAkUAR0dudOTNhaMI/2rGJfVMZC7@xxxxxxxxxxxxxxxx 2005-12-15 23:28 -------
+ Adding a begin_critical_section() to lputuser() is not the correct solution.
+ This problem happens because a mutex is never opened during the attempts to
+ create the base system rooms, because no user is logged in and lgetuser()
+ returns without locking.
+
+ As it turns out, we don't even need to lock the user table during this
operation
+ because nothing is going to get written to it. So we don't. This fixes the
+ problem. As a further optimization, we skip that whole section of code if no
+ user is logged in.

Was this page helpful?

Thread at a glance:

Previous Message by Date: click to view message preview

(no subject)

I haven't tried this in my environment yet. I do know that I could not log into Citadel using the account that already exists on the OS.. but I don't know if I tried logging in via the same account.

Next Message by Date: click to view message preview

[Bug 148] application frame doesn't keep focus?

http://bugzilla.citadel.org/show_bug.cgi?id=148 *** shadow/148 Sat Jun 25 02:55:23 2005 --- shadow/148.tmp.16152 Thu Dec 15 23:29:49 2005 *************** *** 3,10 **** Version: 2.12 Platform: PC OS/Version: Linux ! Status: NEW ! Resolution: Severity: normal Priority: P2 Component: WebCit --- 3,10 ---- Version: 2.12 Platform: PC OS/Version: Linux ! Status: RESOLVED ! Resolution: INVALID Severity: normal Priority: P2 Component: WebCit *************** *** 17,19 **** --- 17,22 ---- i'm neither able to scroll using the mouse weel, nor cursor keys. this is verry anoying. don't know wether its my firefox or something else. but allways having to catch the scroll-thumb or the other stuff is awsome. + + ------- Additional Comments From ajc-1dPMbAkUAR0dudOTNhaMI/2rGJfVMZC7@xxxxxxxxxxxxxxxx 2005-12-15 23:29 ------- + This is a bug in Firefox and it was fixed in version 1.5.

Previous Message by Thread: click to view message preview

autologin

"The otherway involves having Citadel recognize the accounts on the host system, and authenticate against the host system's authentication system. If your host system had an account named 'moo', and someone logged into Citadel with a username of 'moo' for the very first time, they'd be asked for a password.. and supposedly the password 'moo' should give would be the one for the host system." Sounds like the exact same functionality that goes away with ./configure --disable-autologin (which is now default afaik, because it confused too many people like me)When autologin is enabled on OS X/Darwin, Citadel recognises the existance of accounts on the host system but is unable to authenticate against host systems passwords at all. I had the same problem on my Linux From Scratch system, until I realised hitting enter when asked for password (using the text client) was the strange fix, so maybe its not a citadel bug. It sounds like a pretty nice thing for isps and corporations trying to implement the holy grail of single sign on, providing the user has a shell account.

Next Message by Thread: click to view message preview

Loading Comments...