summaryrefslogtreecommitdiffstats
path: root/source3/printing/notify.c
Commit message (Collapse)AuthorAgeFilesLines
* tdb_compat: Higher level API fixes.Rusty Russell2011-06-201-1/+1
| | | | | | | | | | | | My previous patches fixed up all direct TDB callers, but there are a few utility functions and the db_context functions which are still using the old -1 / 0 return codes. It's clearer to fix up all the callers of these too, so everywhere is consistent: non-zero means an error. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
* s3-talloc Change TALLOC_MEMDUP() to talloc_memdup()Andrew Bartlett2011-06-091-2/+2
| | | | | Using the standard macro makes it easier to move code into common, as TALLOC_MEMDUP isn't standard talloc.
* s3-talloc Change TALLOC_P() to talloc()Andrew Bartlett2011-06-091-4/+4
| | | | | Using the standard macro makes it easier to move code into common, as TALLOC_P isn't standard talloc.
* s3-talloc Change TALLOC_ARRAY() to talloc_array()Andrew Bartlett2011-06-091-1/+1
| | | | | Using the standard macro makes it easier to move code into common, as TALLOC_ARRAY isn't standard talloc.
* s3: only include tdb headers where needed.Günther Deschner2011-05-061-0/+1
| | | | Guenther
* More simple const fixes.Jeremy Allison2011-05-051-1/+1
|
* s3-messages: make ndr_messaging.h part of messages.h.Günther Deschner2011-03-301-1/+0
| | | | Guenther
* s3-messages: only include messages.h where needed.Günther Deschner2011-03-301-0/+1
| | | | Guenther
* s3-printing: isolate print notification prototypes better.Günther Deschner2011-02-221-0/+1
| | | | Guenther
* s3-spoolss: dont overwrite location change notify.Günther Deschner2010-10-011-0/+13
| | | | Guenther
* s3: Lift the server_messaging_context from notify_printer_bynameVolker Lendecke2010-08-081-2/+5
|
* s3: Lift the server_messaging_context from notify_printer_locationVolker Lendecke2010-08-081-2/+4
|
* s3: Lift the server_messaging_context from notify_printer_portVolker Lendecke2010-08-081-2/+4
|
* s3: Lift the server_messaging_context from notify_printer_printernameVolker Lendecke2010-08-081-2/+4
|
* s3: Lift the server_messaging_context from notify_printer_sharenameVolker Lendecke2010-08-081-2/+4
|
* s3: Lift the server_messaging_context from notify_printer_commentVolker Lendecke2010-08-081-2/+4
|
* s3: Lift the server_messaging_context from notify_printer_driverVolker Lendecke2010-08-081-2/+4
|
* s3: Lift the server_messaging_context from notify_job_submittedVolker Lendecke2010-08-081-2/+4
|
* s3: Lift the server_messaging_context from notify_job_nameVolker Lendecke2010-08-081-2/+4
|
* s3: Lift the server_messaging_context from notify_job_usernameVolker Lendecke2010-08-081-2/+4
|
* s3: Lift the server_messaging_context from notify_job_total_pagesVolker Lendecke2010-08-081-3/+4
|
* s3: Lift the server_messaging_context from notify_job_total_bytesVolker Lendecke2010-08-081-3/+4
|
* s3: Lift the server_messaging_context from notify_job_statusVolker Lendecke2010-08-081-4/+4
|
* s3: Lift the server_messaging_context from notify_job_status_bynameVolker Lendecke2010-08-081-4/+8
|
* s3: Lift the server_messaging_context from notify_printer_statusVolker Lendecke2010-08-081-4/+4
|
* s3: Lift the server_messaging_context from notify_printer_status_bynameVolker Lendecke2010-08-081-5/+7
|
* s3: Lift the server_messaging_context from send_notify_field_bufferVolker Lendecke2010-08-081-4/+16
|
* s3: Lift the server_messaging_context from send_notify_field_valuesVolker Lendecke2010-08-081-7/+16
|
* s3: Lift the server_messaging_context from send_spoolss_notify2_msgVolker Lendecke2010-08-081-8/+11
|
* s3: Lift the server_messaging_context from print_notify_event_send_messagesVolker Lendecke2010-08-081-2/+5
|
* s3-build: avoid to globally include printing and spoolss headers.Günther Deschner2010-07-311-0/+2
| | | | | | This shrinks precompiled headers by 3MB and will slightly speed up any build. Guenther
* s3: Remove the pointless SERVICE macroVolker Lendecke2010-06-131-7/+7
|
* s3:misc make use of server_[event/messaging]_context directlyAndreas Schneider2010-06-101-3/+3
| | | | | Untangle these functions from smbd specific dependencies so they can be freely used in multiple servers.
* s3: only include gen_ndr headers where needed.Günther Deschner2010-05-061-0/+1
| | | | | | | | | | | | | | | | | This shrinks include/includes.h.gch by the size of 7 MB and reduces build time as follows: ccache build w/o patch real 4m21.529s ccache build with patch real 3m6.402s pch build w/o patch real 4m26.318s pch build with patch real 3m6.932s Guenther
* s3-spoolss: Use const values for notify functions.Andreas Schneider2010-04-231-6/+6
| | | | Signed-off-by: Günther Deschner <gd@samba.org>
* s3-spoolss: use printer and job notify enums provided by idl.Günther Deschner2009-03-181-15/+15
| | | | Guenther
* s3-spoolss: fix notify_printer_status_byname.Günther Deschner2009-02-241-1/+3
| | | | | | | | | | | | | | | | | | | This took me almost a week to find, so here a little longer explanation: When a windows client registers printer *status* change notifies using spoolss_RemoteFindFirstChangeNotify, it registers them to a print server handle, not a printer handle. We were then correctly monitoring the printer status changes but were sending out the spoolss_RouterReplyPrinterEx via the back-channel connection with job_id set to 0 (which we only may do for monitored printer change status notifies on printer handlers, not print server handles). Windows was then showing a new empty dummy printer icon in the explorer as it cannot route the notify event to the approriate local handle. It also discarded the content of the notify event message of course. With this, printer change notify for pausing, resuming and purging printers nicely works again here. Jerry, Tim and all other printing gurus, please check. Guenther
* s3:printing: make some functions static and use tevent functionsStefan Metzmacher2009-01-221-8/+12
| | | | metze
* s3:events: change event_add_timed() prototype to match samba4Stefan Metzmacher2009-01-051-2/+1
| | | | metze
* Fix a spinning smbd when printingVolker Lendecke2008-12-301-1/+1
| | | | | | Without this, we end up adding more than one timed event. In the event handler print_notify_event_send_messages() only one event will be deleted, all others will fire indefinitely.
* Simply our main loop processing. A lot :-). Correctly use events for all the ↵Jeremy Allison2008-10-031-0/+26
| | | | | | | | previous "special" cases. A step on the way to adding signals to the events and being able to merge the S3 event system with the S4 one. Jeremy.
* RIP BOOL. Convert BOOL -> bool. I found a few interestingJeremy Allison2007-10-181-6/+6
| | | | | | | | bugs in various places whilst doing this (places that assumed BOOL == int). I also need to fix the Samba4 pidl generation (next checkin). Jeremy. (This used to be commit f35a266b3cbb3e5fa6a86be60f34fe340a3ca71f)
* r24069: Fix Coverity ID 368. We would segfault if 0 < data.dsize < 8Volker Lendecke2007-10-101-1/+1
| | | | (This used to be commit fa536325681971307661b5d4efde3e8e54f3eca5)
* r23784: use the GPLv3 boilerplate as recommended by the FSF and the license textAndrew Tridgell2007-10-101-2/+1
| | | | (This used to be commit b0132e94fc5fef936aa766fb99a306b3628e9f07)
* r23779: Change from v2 or later to v3 or later.Jeremy Allison2007-10-101-1/+1
| | | | | Jeremy. (This used to be commit 407e6e695b8366369b7c76af1ff76869b45347b3)
* r23112: Trim down the message.c API slightly: The messages_pending_for_pid ↵Volker Lendecke2007-10-101-8/+1
| | | | | | | | | | | | is now replaced by MSG_FLAG_LOWPRIORITY or'ed into the msg_type. To enable this, changed the msg_type definitions to hexadecimal. This way we could theoretically add the MSG_FLAG_NODUPLICATES again, but I would rather not do this, because that one is racy and can't be guaranteed at all. (This used to be commit 3f5eb8a9600839a9f9c44c553f0bda6df22b30b0)
* r23055: Rewrite messages.c to use auto-generated marshalling in the tdb. I'mVolker Lendecke2007-10-101-1/+2
| | | | | | | | | | | | doing this because for the clustering the marshalling is needed in more than one place, so I wanted a decent routine to marshall a message_rec struct which was not there before. Tridge, this seems about the same speed as it used to be before, the librpc/ndr overhead in my tests was under the noise. Volker (This used to be commit eaefd00563173dfabb7716c5695ac0a2f7139bb6)
* r23023: Get rid of the only caller of message_send_pid_with_timeout(). This ↵Volker Lendecke2007-10-101-5/+13
| | | | | | | | | | | | | | | | | | | | | | replaces the timeouts on the individual message send calls with an overall timeout on all the calls. The timeout in message_send_pid_with_timeout() did not make much sense IMO anyway, because the tdb_fetch() for the messages_pending_for_pid was blocking in a readlock anyway, we "just" did the timeout for the write lock. This new code goes through the full wait for the write lock once and then breaks out of sending the notifies instead of running into the timeout per target. Jerry, please check this! Thanks, Volker (This used to be commit 697099f06e1aa432187f802b9c2632607e3de46e)
* r22868: Replace some message_send_pid calls with messaging_send_pid calls. MoreVolker Lendecke2007-10-101-6/+12
| | | | | tomorrow. (This used to be commit 74fa57ca5d7fa8eace72bbe948a08a0bca3cc4ca)
* r22589: Make TALLOC_ARRAY consistent across all uses.Jeremy Allison2007-10-101-3/+7
| | | | | Jeremy. (This used to be commit 8968808c3b5b0208cbad9ac92eaf948f2c546dd9)
generated by cgit (git 2.34.1) at 2024-11-12 22:02:44 +0000