Home
last modified time | relevance | path

Searched refs:problems (Results 1 – 25 of 552) sorted by relevance

12345678910>>...23

/freebsd-11-stable/usr.sbin/lpr/chkprintcap/
HDchkprintcap.c61 static int problems; /* number of problems encountered */ variable
136 problems++; in main()
159 return (problems); in main()
172 err(++problems, "reading printer database"); in interpret_error()
174 ++problems; in interpret_error()
183 errx(++problems, "unknown printcap library error %d", error); in interpret_error()
226 err(++problems, "malloc(%lu)", (u_long)sizeof *dp); in note_spool_dir()
231 err(++problems, "malloc(%lu)", strlen(pp->printer) + 1UL); in note_spool_dir()
234 err(++problems, "malloc(%lu)", strlen(pp->spool_dir) + 1UL); in note_spool_dir()
259 ++problems; in check_spool_dirs()
[all …]
/freebsd-11-stable/crypto/openssl/util/
HDmkcerts.sh36 echo problems generating PCA request
49 echo problems self signing PCA cert
72 echo problems generating CA request
86 echo problems signing CA cert
109 echo problems generating 512 bit server cert request
123 echo problems signing 512 bit server cert
146 echo problems generating 1024 bit server cert request
160 echo problems signing 1024 bit server cert
183 echo problems generating 512 bit client cert request
197 echo problems signing 512 bit client cert
/freebsd-11-stable/contrib/gdb/gdb/
HDPROBLEMS2 Known problems in GDB 6.1
7 *** Build problems
11 GDB 6.1 is known to have build problems on HP/UX 11.00 using the
86 Since this code is new, it is known to still have a few problems:
99 problems, in particular backtraces through signal handlers do not
102 People encountering problems with these architectures should consult
111 have been updated. People encountering problems should consider
HDTODO10 Below is a list of problems identified during the GDB 5.0 release
11 cycle. People hope to have these problems fixed in 5.1.
20 The following patch will fix the problems with setting breakpoints in
194 filename problems.
/freebsd-11-stable/contrib/ntp/sntp/m4/
HDsntp_problemtests.m44 dnl Some platforms have problems building or running certain tests.
16 AC_MSG_CHECKING([if we want to enable tests with undiagnosed problems])
21 [+ enable tests with undiagnosed problems]
HDntp_problemtests.m44 dnl Some platforms have problems building or running certain tests.
16 AC_MSG_CHECKING([if we want to enable tests with undiagnosed problems])
21 [+ enable tests with undiagnosed problems]
/freebsd-11-stable/crypto/openssl/crypto/des/
HDdes.c371 goto problems; in doencryption()
390 goto problems; in doencryption()
402 goto problems; in doencryption()
452 goto problems; in doencryption()
460 goto problems; in doencryption()
514 goto problems; in doencryption()
540 goto problems; in doencryption()
589 goto problems; in doencryption()
612 problems: in doencryption()
/freebsd-11-stable/contrib/netbsd-tests/lib/libc/regex/data/
HDregress.in1 # past problems, and suspected problems
/freebsd-11-stable/contrib/bzip2/
HDREADME.COMPILATION.PROBLEMS15 bzip2 should compile without problems on the vast majority of
30 can cause problems.
53 any compilation problems which affect bzip2 will also affect spewG.c,
/freebsd-11-stable/contrib/traceroute/
HDCHANGES23 - Fix problems caused by savestr().
53 - Avoid problems when broken routers return 0.0.0.0 as their source
76 - Modified linux specific struct ipovly definition to avoid problems
87 - Rewrite source routing code to eliminate a number of problems on
/freebsd-11-stable/contrib/amd/
HDFAQ19 and problems with specific OSs which affect Amd. All of these text files
25 6. Some problems are known bugs but have not been fixed yet: this are
67 administrators than helping alert them to legitimate problems.
/freebsd-11-stable/contrib/groff/contrib/pdfmark/
HDREADME12 be considered as an alpha release; there are a few problems to be
36 PROBLEMS -- a list of known problems
/freebsd-11-stable/crypto/openssh/
HDaclocal.m418 /* Some math to catch -ftrapv problems in the toolchain */
55 /* Some math to catch -ftrapv problems in the toolchain */
93 /* Some math to catch -ftrapv problems in the toolchain */
/freebsd-11-stable/contrib/gcc/
HDREADME.Portability11 any problems as you come across them.
24 Irix6 "cc -n32" and OSF4 "cc" have problems with constant string
105 unsigned int. This mostly causes problems on 64-bit platforms, where
148 avoids all these problems. Unfortunately, the routines in <string.h>
/freebsd-11-stable/contrib/ee/
HDREADME.ee81 than vendor supplied curses. Unless problems occur during the building
85 If you experience problems with data being displayed improperly, check
98 built. If there are problems encountered, you will be notified about
102 solves the problems of some users, I also have no doubt that some will decry
/freebsd-11-stable/share/doc/papers/malloc/
HDMakefile6 SRCS= abs.ms intro.ms kernel.ms malloc.ms problems.ms alternatives.ms \
/freebsd-11-stable/contrib/opie/
HDREADME45 This should solve the endian problems that were in S/Key.
95 Removed active attack protection support due to patent problems.
125 many of the utmp/wtmp problems people have been having.
148 there are a few problems remaining to be solved). Just about re-wrote
216 you are seeing, but may have new problems of their own (that's why they're
305 the system's termios(4). This can cause problems. If you are having
306 compilation problems that seem to relate to termios and you are using
311 termios(4) problem. We haven't reproduced these problems ourselves
353 plain broken. Solaris has other problems with its telnetd and getty; you may
375 potential for problems and because opieauto uses system features that are not
[all …]
/freebsd-11-stable/contrib/dialog/package/freebsd/
HDpkg-descr5 "Initially, I made fixes and reviewed the code to ensure that problems
/freebsd-11-stable/contrib/tcp_wrappers/
HDREADME.IRIX20 restarting inetd does not solve all problems.
39 (5) When an IRIX 5.2 system is a NIS client, it can have problems with
/freebsd-11-stable/contrib/sendmail/src/
HDSECURITY17 This has been demonstrated by recent OS problems which have
19 as a vector. One way to minimize the possibility of such problems
39 avoid problems with a world-writable directory. It is however
45 and hence is not open to system configuration/OS problems or at
/freebsd-11-stable/contrib/apr-util/
HDREADME.FREETDS2 It is known to have problems, and we are not able to maintain it.
/freebsd-11-stable/share/i18n/csmapper/APPLE/
DUCS%DEVANAGA.src177 # WIDTH NON-JOINER in Unicode. However, this causes problems with
181 # problems.
202 # sequence 0xC6 0xE9. This leads to some roundtrip problems. First
203 # note that we have the following mappings without such problems:
214 # However, those mappings above cause roundtrip problems for the
DDEVANAGA%UCS.src177 # WIDTH NON-JOINER in Unicode. However, this causes problems with
181 # problems.
202 # sequence 0xC6 0xE9. This leads to some roundtrip problems. First
203 # note that we have the following mappings without such problems:
214 # However, those mappings above cause roundtrip problems for the
/freebsd-11-stable/contrib/nvi/cl/
HDREADME.signal43 and obviously no reentrancy problems. The down side is that it's easy
57 2: Run in cbreak mode. There are two problems in this area. First, the
85 problems because it didn't use curses.) It entered signals following
126 There are a couple of other problems to consider.
143 Second, SIGTSTP has its own little problems. It's broadcast to the entire
/freebsd-11-stable/contrib/top/
HDFAQ52 Top should not experience any problems with the transition to the year
78 there are no security problems associated with this configuration. The
215 time errors. There appear to be problems with the include files,
222 copies of version 3.5 had additional problems when compiled with gcc.
247 23. I'm still stuck. To whom do I report problems with top?"
249 The most common problems are caused by top's sensitivity to internal kernel

12345678910>>...23