summaryrefslogtreecommitdiff
path: root/source3/smbd/process.c
AgeCommit message (Collapse)AuthorFilesLines
2010-08-17s3: Lift smbd_server_fd() from read_smb_length_return_keepaliveVolker Lendecke1-1/+5
2010-08-17s3: Lift smbd_server_fd() from read_fd_with_timeout()Volker Lendecke1-1/+16
2010-08-17s3: Remove smbd_server_fd() from write_data()Volker Lendecke1-3/+20
This completely removes the DEBUG(0, ..) error message from write_data(). I've gone through all callers of write_data() and made sure that they have their own equivalent error message printing.
2010-08-16s3: Remove smbd_server_fd() from smbd_processVolker Lendecke1-8/+8
2010-08-16s3: Remove smbd_server_fd() from smbd_echo_loopVolker Lendecke1-1/+1
2010-08-16s3: Remove smbd_server_fd() from smbd_echo_readerVolker Lendecke1-2/+2
2010-08-16s3: Remove smbd_server_fd() from smbd_echo_replyVolker Lendecke1-5/+3
2010-08-16s3: Remove smbd_server_fd() from keepalive_fnVolker Lendecke1-1/+1
2010-08-16s3: Remove smbd_server_fd() from smbd_server_connection_handlerVolker Lendecke1-1/+1
2010-08-16s3: Remove smbd_server_fd() from smbd_server_connection_read_handlerVolker Lendecke1-2/+2
2010-08-16s3: Remove smbd_server_fd() from chain_replyVolker Lendecke1-2/+2
2010-08-16s3: Remove smbd_server_fd() from construct_replyVolker Lendecke1-2/+2
2010-08-16s3: Remove smbd_server_fd() from switch_messageVolker Lendecke1-1/+1
2010-08-16s3: Remove smbd_server_fd() from smbd_server_connection_loop_onceVolker Lendecke1-2/+2
2010-08-16s3: Remove smbd_server_fd() from receive_smb_raw_talloc_partial_readVolker Lendecke1-1/+1
2010-08-16s3: Remove get_client_fd()Volker Lendecke1-1/+1
2010-08-13s3: Fix some error messagesVolker Lendecke1-1/+1
2010-08-13s3-smbd: Move rpc services init to smbd parent.Andreas Schneider1-42/+1
The move to the parent makes it possible to use an internal rpc pipe really early and as we migrated serveral parts of samba to rpc function this is required. This should speed up the fork of a smbd a bit cause the rpc services are already running. We still have several problems here which aren't solved. We don't have a dependency tree here. For example we have to make sure that the registry is initialized before we can use the winreg pipe. The spoolss server requires winreg, so we have to start winreg before we can start the spoolss server. I'm sure there are more dependencies. Signed-off-by: Simo Sorce <idra@samba.org>
2010-08-12s3: Reduce the load on the echo handlerVolker Lendecke1-0/+2
If the parent is fast enough, the echo handler should not step in. When the socket becomes readable, the echo handler goes to sleep for a second. If within that second, the parent has picked up the SMB request from the net, the echo handler will just go back to select().
2010-08-12s3: Slightly simplify the logic in smbd_server_echo_handlerVolker Lendecke1-1/+4
2010-08-12s3: Slightly simplify the logic in smbd_server_connection_handlerVolker Lendecke1-1/+4
2010-08-12s3: ?true:false is a *bit* pointless :-)Volker Lendecke1-1/+1
2010-08-08s3: Remove the smbd_messaging_context from spoolss_init_cbVolker Lendecke1-2/+4
2010-08-08s3: Remove some smbd_messaging_context references from smbd_processVolker Lendecke1-7/+7
2010-08-08s3: Pass sconn to smbd_processVolker Lendecke1-28/+28
2010-08-08s3: Lift the server_messaging_context from housekeeping_fnVolker Lendecke1-3/+6
2010-08-08s3: Lift the server_messaging_context from check_reloadVolker Lendecke1-4/+4
2010-08-08s3: Make check_reload() staticVolker Lendecke1-1/+1
2010-08-08s3: Lift the server_messaging_context from update_monitored_printq_cacheVolker Lendecke1-1/+1
2010-08-08s3: Lift the smbd_messaging_context from smbd_setup_sig_hup_handlerVolker Lendecke1-6/+4
2010-08-08s3: Lift the smbd_messaging_context from smbd_sig_hup_handlerVolker Lendecke1-2/+4
2010-08-08s3: Lift the smbd_messaging_context from reload_servicesVolker Lendecke1-3/+3
2010-08-08s3: Lift the smbd_messaging_context from reload_printersVolker Lendecke1-1/+1
2010-08-08s3: Lift the smbd_messaging_context from nt_printing_tdb_migrateVolker Lendecke1-1/+1
2010-08-07s3: Remove some references to smbd_messaging_context()Volker Lendecke1-5/+6
2010-07-28smbd: Fix build warningSimo Sorce1-1/+1
2010-07-27s3-printing: Added automatic migration of printing tdbs.Andreas Schneider1-2/+26
Signed-off-by: Jim McDonough <jmcd@samba.org>
2010-07-05s3: Pass procid_self() explicitly to messaging_ctdbd_connection()Volker Lendecke1-1/+1
2010-07-04s3: Pass the new server_id through reinit_after_forkVolker Lendecke1-1/+2
2010-06-28 s3: Change exit on immediate socket failure.Ira Cooper1-4/+4
This change makes it so socket errors early in the smbd child process cause orderly exits not coredumps. Signed-off-by: Jeremy Allison <jra@samba.org>
2010-06-12s3: Explicitly pass sconn to [remove|schedule]_deferred_open_message_smb2Volker Lendecke1-2/+2
2010-06-12s3: Explicitly pass sconn to open_was_deferred_smb2Volker Lendecke1-1/+1
2010-06-12s3: Remove smbd_server_conn from switch_messageVolker Lendecke1-1/+1
2010-06-12s3: Explicitly pass sconn to is_valid_writeX_bufferVolker Lendecke1-1/+2
2010-06-12s3: Pass sconn explicitly to reply_specialVolker Lendecke1-1/+1
2010-06-12s3: Use "sconn" argument in smbd_[un]lock_socket_internalVolker Lendecke1-8/+8
Metze, please check!
2010-06-12s3: Pass sconn to init_smb_request()Volker Lendecke1-5/+7
2010-06-12s3: Add "smbd_server_connection" to smb_requestVolker Lendecke1-0/+1
2010-06-11s3: Fix starving the echo responderVolker Lendecke1-0/+11
When both the echo responder and the 445 socket want to send stuff to the worker smbd, the select loop is not fair. It always chooses the smaller file descriptor to work on. This can mean that on a busy system the echo responder never gets around to feed its stuff to the parent. This fix chooses the async echo responder socket when both the 445 and the echo responder socket are readable. Yes, it is a very hackish fix which is required *now* I think. The proper fix would be to either assign priorities to fd's in tevent, or the from my point of view better fix would be to make tevent kindof round-robin. Round-robin would mean that whenever a fd has been dealt with, it is taken off the list of interested sockets, and only if no other socket is active, all of the ones waiting are put back. This is a bit like EPOLL_ONESHOT, which I would like to use for this in the epoll case. Although, I need to do some research if maybe epoll already guarantees round-robin, I did not find anything in the docs yet. Volker
2010-06-09Rename "allow_smb2" -> "using_smb2" and make the usage clearer.Jeremy Allison1-9/+18