| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for calculating the job number for a job based on the control-file name.
We might receive cf-files named by other implementations of lpr, where
the job number shown by lpq would not match the job number that other
commands expected for the same name.
This also uses a newer algorithm for determining a job number, to avoid
problems caused when a control-file is named using an IP address, instead
of the hostname.
This also moved the declaration if isowner() from lp.h to rmjob.c. When I
went to change the parameters, I noticed that rmjob.c was the only source
file which uses it.
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
addresses and scope IDs.
MFC after: 3 weeks
|
|
|
|
|
|
|
|
|
|
|
|
| |
than a colon, so don't allow whitespace in program names. To be
consistent with hostnames, don't allow whitespace in the program
name specifiers in syslog.conf either.
(The first change is by Markus from the PR, the second is mine.)
PR: 68691
Submitted by: Markus Oestreicher <m.oe@x-trader.de>
MFC after: 3 weeks
|
|
|
|
|
|
|
|
| |
(Broken in rev. 1.52.)
PR: 75471
Submitted by: Jon Simola
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
disk. This is main reason why sysinstall presents SCSI CDROM to
available disks in Fdisk/Label menu. In addition, adding a blank
SCSI CDROM to the menu generates floating point exception in sparc64.
Disk_Names() just extracts sysctl "kern.disks". Why GEOM treats SCSI
CDROM as a disk is beyond me and that should be investigated.
For temporary workaround, ignore SCSI CDROM device.
PR: sparc64/72962
Tested by: R. Tyler Ballance < tyler AT tamu DOT edu>
MFC after: 1 week
|
| |
|
|
|
|
| |
so that "eject" following it can happen.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
/etc/make.conf:
NOALIAS -> retired (support provided by PPP_NO_NAT)
NOATM -> PPP_NO_ATM (also subject to NO_ATM global)
NODES -> PPP_NO_DES (support was broken, now recovered)
NOI4B -> PPP_NO_I4B (also subject to NO_I4B global)
NOKLDLOAD -> PPP_NO_KLDLOAD
NONAT -> PPP_NO_NAT
NONETGRAPH -> PPP_NO_NETGRAPH
NOPAM -> PPP_NO_PAM (will be subject to NO_PAM global)
NORADIUS -> PPP_NO_RADIUS
NOSUID -> retired (support provided by PPP_NO_SUID)
PPP_NOSUID -> PPP_NO_SUID
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
NOLIBPTHREAD -> NO_LIBPTHREAD
NOLIBTHR -> NO_LIBTHR
|
|
|
|
| |
OK'ed by: core
|
|
|
|
|
|
|
|
| |
a long (UT_NAMESIZE) login names.
PR: bin/75259
Submitted by: Matthew D.Fuller
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
| |
the file will be created with the right access, if the call to open()
does create it. Also fix the other call to umask() to turn off
"write others", just as a matter of general safety.
PR: 74418
MFC after: 4 days
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
sure the data file has been completely transfered before starting to
print it. This is needed because some implementations of lpr will send
the control-file for a print job before sending the matching data-files,
and that can cause problems if the receiving host is a busy print-server.
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
that you can get around it by double-quoting them.
PR: 42762
Submitted by: AIDA Shinra <aida-s@jcom.home.ne.jp>
Discussed with: brian
|
|
|
|
| |
Submitted by: Craig Rodrigues
|
|
|
|
|
|
| |
- bump .Dd
MFC after: 3 days
|
|
|
|
|
| |
PR: 74972
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
This allows LCP ECHOs to be enabled independently of LQR reports.
Note: This introduces a change in the default behaviour (search for lqr and
echo in the man page). I'll update UPDATING to reflect this.
PR: 74821
|
| |
|
|
|
|
|
| |
PR: bin/73105
MFC after: 2 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
administrator specified number.
The implementation in our version transmits extra zero byte that is a
violation of the Microsoft PPP Callback Control Protocol section 3.2[1].
This can lead to incorrect behavior on certain devices, as reported
in bin/50613.
Confirmed with: cbcp.c in ppp's cvs, rev. 1.4 and 1.15 [2]
Submitted by: Dmitry Pryanishnikov <dmitry at atlantis.dp.ua>
PR: bin/50613
[1] http://www.dsl.gr.jp/~manabe/PPxP/doc/Standards/draft-gidwani-ppp-callback-cp-00.txt
[2] http://cvs.samba.org/cgi-bin/cvsweb/ppp/pppd/cbcp.c
http://www.samba.org/cvs.html
|
|
|
|
| |
for NFS locking.
|
|
|
|
|
|
|
|
| |
Add ``disable NAS-IP-Address'' and ``disable NAS-Identifier'' options to
support pre-rfc2865 RADIUS servers.
This pushes our enable/disable items over the 32 bit limit, so reoganise
things to allow a bunch more options.
Go to version 3.4.1 so that any compatability problems can be identified.
|
|
|
|
|
| |
PR: bin/71615
Submitted by: Craig Rodrigues (original patch by Dan Lukes)
|
|
|
|
| |
including other headers.
|
|
|
|
|
|
|
|
|
| |
to deal with a big number of nodes.
Submitted by: archie
Approved by: archie
Reported and tested: Konstantin Timashkov
MFC after: 1 month
|
|
|
|
|
|
|
| |
units (as specified in _BIF). (noted by Bruno Ducrot)
o In looking in the standard, if the cap numbers are 0xffffffff, then acpi
is reporting unknown for that field. Report unknown numbers properly.
o Update the state to reflect charging, discharging and critical.
|
|
|
|
|
|
|
|
| |
my patches for this information. Commit my more complete version.
This version isn't complete yet, since some details aren't handled
right just yet.
Poaching by: phk
|
|
|
|
|
| |
The -i code doesn't really belong here in the first place I would think,
but keep it together for now.
|
|
|
|
|
| |
PR: 73879
Submitted by: Steve Kargl <sgk@troutmask.apl.washington.edu>
|
|
|
|
|
| |
PR: 73878
Submitted by: Steve Kargl <sgk@troutmask.apl.washington.edu>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
hence bump it to 6.
Note that the last commit message was not quite accurate. While the
assumption exists in the code, it's not possible to have an
uninitialized p there because if lflag is set when username is NULL
then execution would be terminated earlier.
|
|
|
|
|
| |
initialized with NULL, while it is not. So let's initialize
it.
|
|
|
|
|
|
|
|
|
| |
accidentally removed in v. 1.211.
Submitted by: Olafur Osvaldsson <oli@isnic.is>
PR: bin/73692
MFC after: 1 week
Approved by: trhodes
|