summaryrefslogtreecommitdiff
path: root/source3/rpc_client/rpc_transport_smbd.c
AgeCommit message (Collapse)AuthorFilesLines
2010-03-29s3:rpc_client: remove more unused codeStefan Metzmacher1-10/+0
metze
2010-03-29s3:rpc_client: add set_timeout hook to rpc_cli_transportStefan Metzmacher1-0/+19
metze
2010-03-29s3:rpc_client: add rpccli_is_connected()Stefan Metzmacher1-6/+70
metze
2010-01-06s3: Fix infinite loop in NCACN_IP_TCP asa there is no timeout. Assume ↵Bo Yang1-0/+10
lsa_pipe_tcp is ok but network is down, then send request is ok, but select() on writeable fds loops forever since there is no response. Signed-off-by: Bo Yang <boyang@samba.org>
2009-04-08Convert rpc_transport_smbd_init to tevent_reqVolker Lendecke1-34/+32
2009-04-08Convert rpc_cli_smbd_conn_init to tevent_reqVolker Lendecke1-37/+34
2009-04-08Convert get_anon_ipc to tevent_reqVolker Lendecke1-40/+35
2009-04-08Convert rpc_transport_np_init to tevent_reqVolker Lendecke1-7/+7
2009-04-06Convert cli_tcon_andx to tevent_reqVolker Lendecke1-13/+10
2009-04-06Convert cli_negprot to tevent_reqVolker Lendecke1-7/+7
2009-04-06Convert cli_session_setup_guest to tevent_reqVolker Lendecke1-12/+13
2009-04-05Keep the forked-smbd stdout reader around longerVolker Lendecke1-3/+8
2009-04-05Ensure 0-termination for the forked-smbd debug outputVolker Lendecke1-0/+1
2009-04-05Pass the current debuglevel down to the forked smbdVolker Lendecke1-1/+2
2009-03-24Convert rpc_cli_transport->write to tevent_reqVolker Lendecke1-24/+22
2009-03-24Convert rpc_cli_transport->read to tevent_reqVolker Lendecke1-25/+22
2009-02-02Next step disentangling async_req from NTSTATUSVolker Lendecke1-2/+2
Now I need to document this :-)
2009-02-01Split up async_req into a generic and a NTSTATUS specific partVolker Lendecke1-15/+15
2009-01-30Add the "SMBD" rpc transportVolker Lendecke1-0/+694
The idea of this is that all client utils like smbpasswd and also for example "net join" do not access our internal databases like passdb and secrets.tdb directly anymore but pass everything throught the well-established RPC interfaces. The way you use this is the following: With rpc_cli_smbd_conn_init() or its async variant you initialize a "struct rpc_cli_smbd_conn". This structure is the link to a freshly forked smbd, ready to be used for RPC services. You should only ever have one such structure in your program. More don't hurt, but are plainly unnecessary. If you want to use the SAMR pipe to change a passwort, you connect to that pipe with rpc_pipe_open_local. Do you normal rpccli_samr calls on that and your locally forked smbd will connect to passdb for you. GD, this might make the distinction between the _l and _r calls in libnetapi mostly unnecessary. At least it is intended to do so... :-)