| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
of them to keep better track of which-is-which (multiple variables were
named 'pid'). Moved a global pid-variable into the only routine that
used it. Net result: fixes two compile-time warnings...
MFC after: 2 weeks
|
|
|
|
|
|
| |
simply getting the indentation right when the statement wraps).
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
|
| |
value in wstatus is not related to the process that we care about.
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
standard handling of wait()-related routines.
Submitted by: mike
MFC after: 2 weeks
|
| |
|
|
|
|
|
| |
Discussed with: bde, obrien
MFC after: 10 days
|
| |
|
| |
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
to (void *) to satisfy some stricter warning-level checks in the new
gcc (on sparc64).
Reviewed by: obrien
MFC after: 4 days
|
|
|
|
|
|
|
| |
connect() to the socket for lpd. Tell them this error probably means that
the master 'lpd' process is not running.
MFC after: 4 days
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a boolean option, and if it is specified in a print queue
for a remote host, it causes lpd to resend the data file for each
copy the user requested on 'lpr -#n'. This is useful for network
printers which accept lpd-style jobs, but which ignore the control
file (and thus they ignore any request for multiple copies).
PR: 25635
Reviewed by: short review on freebsd-audit
MFC after: 6 days
|
|
|
|
|
|
| |
new gcc (on sparc64).
MFC after: 4 days
|
|
|
|
|
|
| |
new gcc (on sparc64).
MFC after: 4 days
|
|
|
|
|
| |
Also change one case of blatant __progname abuse (several more remain)
This commit does not touch anything in src/{contrib,crypto,gnu}/.
|
| |
|
|
|
|
|
|
| |
default values are underlined (instead of using fake double-quotes).
MFC after: 4 days
|
|
|
|
|
|
|
|
| |
for `tf' (troff filter), and add a cross-reference to chkprintcap in some
lpr-related man pages.
Submitted by: dwmalone
MFC after: 4 days
|
| |
|
|
|
|
|
|
|
|
|
|
| |
for what is currently the '-p' parameter. '-s' is what NetBSD
used (and they implemented it before I added -p in FreeBSD), and
it also matches the '-s' option in syslogd. Someone in OpenBSD
land had also talked about adding a '-s' option, but it hasn't
happened yet.
MFC after: 5 days
|
|
|
|
|
|
| |
line is using strlcpy instead of strncpy.
MFC after: 4 days
|
|
|
|
|
| |
Obtained from: NetBSD, OpenBSD
MFC after: 4 days
|
|
|
|
|
|
| |
execute a given filter.
MFC after: 4 days
|
|
|
|
|
|
|
|
|
| |
"confused" about it being unassigned. In fact, gcc was right. Fix the
real problem by setting that variable before break-ing out of a select
statement so gcc is happy, and then remove the unnecessary assignment.
Reported by: a user wondering why lpd syslog-ed about "compiler confusion"
MFC after: 12 days
|
|
|
|
| |
MFC after: 12 days
|
|
|
|
|
|
|
|
|
| |
input file and any temporary (filter) file are closed upon return, and
that is generally done at the end of the routine. This should make it
easier for a later update (not yet written) to implement a "resend_copies"
option.
MFC after: 12 days
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
remote machines. Now they really are handled *exactly* the same as
input filters (if=) for remote queues, except that they are started
with a different set of parameters. This should fix a few subtle
bugs in output-filter processing on such queues. It is a pretty
significant re-arranging of sendfile(), moving some of it to a new
execfilter() routine.
PR: 36552
Reviewed by: no screams from freebsd-audit
MFC after: 12 days
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"skimming thru" the printcap file looking for some common mistakes that
people make. These are the kinds of mistakes where the printcap file
probably looks correct to human eyes, but is wrong in some subtle way
which causes a problem in some queue definitions. The program treats
these as "warnings" not "errors".
Note that I'm flexible on the m.f.c. schedule, if people would rather
this waited until after 4.5-release.
Reviewed by: no screams from freebsd-audit freebsd-print@bostonradio.org
MFC after: 4 days
|
|
|
|
|
|
|
|
|
|
|
| |
for a remote print job. This change comes from OpenBSD (who got it from
Sebastian Krahmer of SuSE). In OpenBSD this avoids a tiny theoretical
security issue, but that security issue does not exist in FreeBSD's lpr
due to the changes which added 'ctl_renametf()' just before 4.4-release.
This change is still worth doing in our version, but it isn't fixing a
security issue.
MFC after: 4 days
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
'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
|
|
|
|
| |
MFC after: 4 days
|
|
|
|
| |
MFC after: 4 days
|
|
|
|
|
|
| |
warnings about conflict with a global variable used by 'lprm'.
MFC after: 4 days
|
|
|
|
|
|
|
| |
definitions to the same format used in other lpr source files, and by
adding parenthesis to the right spot in one 'if' statement.
MFC after: 4 days
|
|
|
|
| |
MFC after: 4 days
|
|
|
|
| |
MFC after: 4 days
|
| |
|
|
|
|
|
|
|
|
|
|
| |
'lpc tclean'. In some obscure cases, the previous version could cause a
valid user job to be removed (by 'clean'), due to invalid assumptions in
the sort routine. This was a rare problem, unless ctlinfo.c is compiled
with 'LEAVE_TMPCF_FILES' turned on (to check what that rtn was doing).
Reviewed by: Lack of outcry on -audit and freebsd-print@bostonradio.org
MFC after: 10 days
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
into thinking that there is a print-queue called 'xterm'...
Reviewed by: short discussion on freebsd-stable
MFC after: 1 week
|
|
|
|
|
|
| |
This is not "useless", as one may have non-default
setting for BINOWN in make.conf, and we still want
these to be installed setuid root in this case.
|
|
|
|
|
| |
Submitted by: millert@openbsd.org, gad
Reported by: X-Force <xforce@iss.net>
|
|
|
|
| |
with a trailing zero-width space: `e.g.\&'.
|
|
|
|
|
|
|
| |
Avoid using parenthesis enclosure macros (.Pq and .Po/.Pc) with plain text.
Not only this slows down the mdoc(7) processing significantly, but it also
has an undesired (in this case) effect of disabling hyphenation within the
entire enclosed block.
|
|
|
|
|
|
|
|
|
| |
correct the error-checking that was there. With the old code, an error
return from getpwuid(daemon_user) could turn the lpd process into a very
effective fork-bomb...
Reviewed by: freebsd-audit freebsd-print (a little...)
MFC after: 6 days
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
| |
appropriate, and using '("%lu", (unsigned long)asizeval)' when printing
something of type size_t.
MFC after: 1 week
|