|
Revision tags: release/14.1.0, release/13.3.0, release/14.0.0 |
|
| #
1d386b48 |
| 16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
Remove $FreeBSD$: one-line .c pattern
Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/
|
| #
4d846d26 |
| 10-May-2023 |
Warner Losh <imp@FreeBSD.org> |
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of BSD-2-Clause.
Discussed with: pfg MFC After: 3 days Sponsored by: Netflix
show more ...
|
|
Revision tags: release/13.2.0, release/12.4.0, release/13.1.0, release/12.3.0 |
|
| #
840d7237 |
| 19-Nov-2021 |
Gordon Bergling <gbe@FreeBSD.org> |
lpr(1): Fix a typo in a source code comment
-s /debuging/debugging/
MFC after: 3 days
|
|
Revision tags: release/13.0.0, release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0, release/11.2.0 |
|
| #
02e8b7b2 |
| 12-Mar-2018 |
Garance A Drosehn <gad@FreeBSD.org> |
Fix the resource leak of a 'FILE *' which could happen in routine ctl_readcf() if a call to malloc failed.
PR: 204955 Reported by: David Binderman
|
| #
1de7b4b8 |
| 27-Nov-2017 |
Pedro F. Giffuni <pfg@FreeBSD.org> |
various: general adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error
various: general adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error prone - task.
The Software Package Data Exchange (SPDX) group provides a specification to make it easier for automated tools to detect and summarize well known opensource licenses. We are gradually adopting the specification, noting that the tags are considered only advisory and do not, in any way, superceed or replace the license texts.
No functional change intended.
show more ...
|
|
Revision tags: release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0, release/10.3.0, release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0, release/9.2.0, release/8.4.0, release/9.1.0, release/8.3.0_cvs, release/8.3.0, release/9.0.0 |
|
| #
ad1f7851 |
| 13-Apr-2011 |
Garance A Drosehn <gad@FreeBSD.org> |
- Fix the code that matches userids in match_jobspec(). It needs to check the username-for-accounting field (P), not the username-for-headerpage (L). These are usually the same value, except tha
- Fix the code that matches userids in match_jobspec(). It needs to check the username-for-accounting field (P), not the username-for-headerpage (L). These are usually the same value, except that control files do not have the username-for-headerpage field if the user has requested no header page. - Also rename the cji_username field to cji_headruser, to make it clear that the value should only be used for the header page. (aka banner page)
MFC after: 3 weeks
show more ...
|
|
Revision tags: release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0, release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0, release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0, release/7.0.0_cvs, release/7.0.0, release/6.3.0_cvs, release/6.3.0, release/6.2.0_cvs, release/6.2.0, release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0, release/6.0.0_cvs, release/6.0.0, release/5.4.0_cvs, release/5.4.0, release/4.11.0_cvs, release/4.11.0 |
|
| #
e357c6ec |
| 31-Dec-2004 |
Garance A Drosehn <gad@FreeBSD.org> |
Do more extensive checking of the userid field which is read in from the control-file for each print job. This is partially because the previous checks still let through some characters which would
Do more extensive checking of the userid field which is read in from the control-file for each print job. This is partially because the previous checks still let through some characters which would cause trouble for other applications which try to process the resulting userid -- such as accounting programs.
But the main reason is to handle the case where some remote host sends a print job where the given userid is an uppercase-version of the real userid. For that case, lpd will now check for uppercase letters in the userid. If there are any, it will check to see if the given userid (with the uppercase letters) is a valid one. If it is *not* valid, then lpd will change the userid to all-lowercase right when the job is received.
MFC after: 2 weeks
show more ...
|
|
Revision tags: release/5.3.0_cvs, release/5.3.0, release/4.10.0_cvs, release/4.10.0, release/5.2.1_cvs, release/5.2.1, release/5.2.0_cvs, release/5.2.0, release/4.9.0_cvs, release/4.9.0 |
|
| #
1f589b47 |
| 14-Jul-2003 |
Garance A Drosehn <gad@FreeBSD.org> |
Take advantage of the common_source/lp.cdefs.h file to change lpr source to use __FBSDID() for setting rcsids. Also fix the format of 'sccsid' lines to consistently match style(9) guidelines.
Revie
Take advantage of the common_source/lp.cdefs.h file to change lpr source to use __FBSDID() for setting rcsids. Also fix the format of 'sccsid' lines to consistently match style(9) guidelines.
Reviewed by: discussed with bde and obrien MFC after: 15 days
show more ...
|
| #
394fd40f |
| 12-Jun-2003 |
Garance A Drosehn <gad@FreeBSD.org> |
Minor improvement to some debugging code that is probably used by no one but me (it's usually #ifdef-ed out).
MFC after: 1 week
|
| #
da464120 |
| 12-Jun-2003 |
Garance A Drosehn <gad@FreeBSD.org> |
When sanity-checking a variable, it's good to check the correct variable...
MFC after: 1 week
|
|
Revision tags: release/5.1.0_cvs, release/5.1.0, release/4.8.0_cvs, release/4.8.0, release/5.0.0_cvs, release/5.0.0, release/4.7.0_cvs, release/4.6.2_cvs, release/4.6.2, release/4.6.1 |
|
| #
d6771428 |
| 12-Jul-2002 |
Garance A Drosehn <gad@FreeBSD.org> |
Move prototypes for ctl_readcf and ctl_freeinf from ctlinfo.c to ctlinfo.h, so the routines can be called by an upcoming change for 'lpc topq/bottomq'.
MFC after: 3 days
|
|
Revision tags: release/4.6.0_cvs |
|
| #
32e56cd1 |
| 25-Apr-2002 |
Garance A Drosehn <gad@FreeBSD.org> |
When using %p to print out pointers to struct's, first cast the values to (void *) to satisfy some stricter warning-level checks in the new gcc (on sparc64).
Reviewed by: obrien MFC after: 4 days
|
|
Revision tags: release/4.5.0_cvs, release/4.4.0_cvs |
|
| #
1fd731fa |
| 28-Nov-2001 |
Garance A Drosehn <gad@FreeBSD.org> |
My recent changes to add the ctl_renametf routine assumed that print job control-files will always start with 'cfA*'. It turns out that some implementations of lpd (such as solaris) may send a contr
My recent changes to add the ctl_renametf routine assumed that print job control-files will always start with 'cfA*'. It turns out that some implementations of lpd (such as solaris) may send a control file which starts with 'cfB*', or really 'cf<anyLetter>*'. Although such filenames are very odd, we did used to accept them. This changes ctl_renametf to work correctly with them, and fixes up 'lpc clean' to match.
PR: bin/32183 MFC after: 10 days
show more ...
|
| #
21ecfd4a |
| 27-Nov-2001 |
Garance A Drosehn <gad@FreeBSD.org> |
Change the recently-added 'o'-processing so it maps to 'l' instead of 'f'. 'l' ("plain text which includes control characters") is somewhat more appropriate for 'o' ("postscript files"), and in fact
Change the recently-added 'o'-processing so it maps to 'l' instead of 'f'. 'l' ("plain text which includes control characters") is somewhat more appropriate for 'o' ("postscript files"), and in fact some printers treat 'l' as a request to print a postscript file.
MFC after: 1 week
show more ...
|
| #
626fb2a6 |
| 20-Sep-2001 |
Garance A Drosehn <gad@FreeBSD.org> |
Add minimal support for "o"-type print-file actions in lpd control files. This was described in the original RFC wrt lpr, but most lpr's do not actually implement it. There is some indication that M
Add minimal support for "o"-type print-file actions in lpd control files. This was described in the original RFC wrt lpr, but most lpr's do not actually implement it. There is some indication that MacOS 10.1 will be using this when sending postscript files to print servers (that is what "o"-type was supposed to signify -- postscript files).
MFC after: 1 week
show more ...
|
| #
442e0eaf |
| 15-Jul-2001 |
Garance A Drosehn <gad@FreeBSD.org> |
Change lpd to perform sanity and safety checks on control files as it receives them from other hosts. This is meant to protect from both nefarious users (which maybe broke into some remote host that
Change lpd to perform sanity and safety checks on control files as it receives them from other hosts. This is meant to protect from both nefarious users (which maybe broke into some remote host that we accept print jobs from), and broken implementations of lpr on other platforms. This is done by changing recvjob.c to call the new ctl_renametf() routine in the new common_source/ctlinfo.[ch] files. This will not affect jobs coming via lpr on the local machine.
Reviewed by: freebsd-print@bostonradio.org & freebsd-audit MFC after: 16 days
show more ...
|