04-03-2020
Bug in New User Registration Process (No Registration Complete Message)
There is bug in the new member registration process.
This bug appeared after we paused registration and moved to the new forums in our initial test mode.
When a new user registers now (here), the registration processes completes (normally) but the "Registration Success" message does not appear in the registration feedback message.
However, the user can login.
I have already retired this code base and do not plan to fix this bug since we will be moving to a new forum soon.
Thank you for your patience.
One option is to disable new user registrations again here, but for now I will leave it "as-is" since we will get the new forums running again soon (we hope!).
This User Gave Thanks to Neo For This Post:
7 More Discussions You Might Find Interesting
1. Forum Support Area for Unregistered Users & Account Problems
I have followed the instructions contained in my confirmation email and when I do I am referred here: https://www.unix.com/register.php?a=act&u=302021451&i=94824252. When I follow the instructions on that screen I am directed to the same error page. Please assist. Thank you in advance. (1 Reply)
Discussion started by: ramiller01
1 Replies
2. Forum Support Area for Unregistered Users & Account Problems
To Whom It May Concern,
I've tried registering, and am unable to do so. The message being returned is that my name choices are being rejected for not meeting some administrator criteria, which is not discernible from the message returned by the board software.
The password I chose was all... (1 Reply)
Discussion started by: username_in_use
1 Replies
3. Forum Support Area for Unregistered Users & Account Problems
i can not register, please help me (1 Reply)
Discussion started by: friender@mail
1 Replies
4. Forum Support Area for Unregistered Users & Account Problems
When I'm trying to register it says that my e-mail adress )is banned by administrator. Why?
Thanks
PS The same problem occurs with other 2 adresses I have (1 Reply)
Discussion started by: Mihail
1 Replies
5. Forum Support Area for Unregistered Users & Account Problems
Unix Admin
Registration process refused two user names.
I may have already registered here and
it's kicking me out because of email address but
giving me username msg.
What's the solution to this?
Thanks (0 Replies)
Discussion started by: Unregistered
0 Replies
6. Forum Support Area for Unregistered Users & Account Problems
Hello Moderators,
Greetings !!
This is regarding my friend to whom I refered this forum to learn UNIX. User didn't receieved any registration email yet, could you please help user. Will be grateful to you on same.
Login name: Gurvinder_Kaur
NOTE: User doesn't have enough bits for... (0 Replies)
Discussion started by: RavinderSingh13
0 Replies
7. What is on Your Mind?
Today I found out that many new user registrations were having trouble logging in.
I spend about three hours debugging this, and I think I fixed the problem.
If anyone registers and has trouble logging in please contact me on Live Chat.
Thanks. (1 Reply)
Discussion started by: Neo
1 Replies
LEARN ABOUT SUNOS
ddi_add_event_handler
ddi_add_event_handler(9F) Kernel Functions for Drivers ddi_add_event_handler(9F)
NAME
ddi_add_event_handler - add an NDI event service callback handler
SYNOPSIS
#include <sys/dditypes.h>
#include <sys/sunddi.h>
int ddi_add_event_handler(dev_info_t *dip, ddi_eventcookie_t cookie, void (*handler)(dev_info_t *, ddi_eventcookie_t, void *, void *), void
*arg, ddi_registration_id_t *id);
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI).
PARAMETERS
dev_info_t *dip
Device node registering the callback.
ddi_eventcookie_t cookie
Cookie returned from call to ddi_get_eventcookie(9F).
void (*handler)(dev_info_t *, ddi_eventcookie_t, void *, void *)
Callback handler responsible for handling an NDI event service notification.
void *arg
Pointer to opaque data supplied by the caller. Typically, this would be a pointer to the driver's softstate structure.
ddi_registration_id_t *id
Pointer to registration ID where a unique registration id will be returned. Registration ID must be saved and used when calling
ddi_remove_event_handler(9F) to unregister a callback.
DESCRIPTION
The ddi_add_event_handler() function adds a callback handler to be invoked in the face of the event specifed by cookie. The process of
adding a callback handler is also known as subscribing to an event. Upon successful subscription, the handler will be invoked by the system
when the event occurs. The handler can be unregistered by using ddi_remove_event_handler(9F).
An instance of a driver can register multiple handlers for an event or a single handler for multiple events. Callback order is not defined
and should assumed to be random.
The routine handler will be invoked with the following arguments:
dev_info_t *dip
Device node requesting the notification.
ddi_eventcookie_t cookie
Structure describing event that occurred.
void *arg
Opaque data pointer provided, by the driver, during callback registration.
void *impl_data
Pointer to event specific data defined by the framework which invokes the callback function.
RETURN VALUES
DDI_SUCCESS
Callback handler registered successfully.
DDI_FAILURE
Failed to register callback handler. Possible reasons include lack of resources or a bad cookie.
CONTEXT
The ddi_add_event_handler() and handler() function can be called from user and kernel contexts only.
ATTRIBUTES
See attributes(5) for a description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Stability Level |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
attributes(5), ddi_get_eventcookie(9F), ddi_remove_event_handler(9F)
Writing Device Drivers
NOTES
Drivers must remove all registered callback handlers for a device instance by calling ddi_remove_event_handler(9F) before detach completes.
SunOS 5.10 62 Nov 2003 ddi_add_event_handler(9F)