Home
last modified time | relevance | path

Searched full:problems (Results 1 – 25 of 1335) sorted by relevance

12345678910>>...54

/freebsd/usr.sbin/lpr/chkprintcap/
H A Dchkprintcap.c59 static int problems; /* number of problems encountered */ variable
63 * Returns the number of problems found.
115 problems = 1; in main()
118 problems = skres->fatalerr; in main()
139 problems++; in main()
165 return (problems); in main()
178 err(++problems, "reading printer database"); in interpret_error()
180 ++problems; in interpret_error()
189 errx(++problems, "unknown printcap library error %d", error); in interpret_error()
197 * problems are noted first. We keep the list sorted by st_dev and
[all …]
/freebsd/share/doc/papers/relengr/
H A D3.t53 and needs wider testing to find more obscure problems.
120 Thus, users upgrading to the new system can anticipate problems
128 other interoperability problems become apparent
130 When all known problems have been resolved, and the system has been
158 they monitor the problems that they encounter.
179 When such problems are found,
193 problems between different utilities.
199 These differences in usage patterns turn up problems that
206 problems back to the site from which they received the distribution,
226 Once the major problems have been attended to,
[all …]
/freebsd/share/doc/smm/06.nfs/
H A D1.t71 .sh 1 "Mount Problems"
73 There are several problems that can be encountered at the time of an NFS
75 from client, etc.) to various interoperability problems between different
89 If problems are encountered,
92 Other server side problems are normally caused by problems with the format
97 with server problems.
143 groups that the user is in, which can cause some accessibility problems.
147 It also reduces the number of actual NFS mount points, alleviating problems
233 alleviate performance problems related to UDP RPC transport.
242 whenever IP fragmentation is causing problems. The best indicator of
[all …]
/freebsd/share/doc/papers/malloc/
H A Dproblems.ms11 The problems
17 a lot of problems arise from its use.
37 The handling of these problems have traditionally been weak.
51 With problems this big and error handling this weak, it is not
52 surprising that problems are hard and time consuming to find and fix.
/freebsd/share/doc/papers/sysperf/
H A D0.t65 had several problems that could severely affect the overall
67 These problems were identified with
71 These benchmarks verified that the problems existed and provided
74 the performance problems encountered and describes
215 \0.2. Security Problems in Utilities
/freebsd/contrib/ntp/html/
H A Ddebug.html22 …es produce only mildly cryptic output and can be very useful in finding problems with configuratio…
23 <p>Some problems are immediately apparent when the daemon first starts running. The most common of …
24 <p>Other problems are apparent in the system log, which ordinarily shows the startup banner, some c…
25 …a partial or complete path exists. Most problems reported to the NTP newsgroup are not NTP problem…
53 …<li>A useful indicator of miscellaneous problems is the <tt>flash</tt> peer variable, which shows …
70 <p>Specific provisions have been built into <tt>ntpd</tt> to cope with these problems. The scheme i…
73 …Problems with symmetric key authentication are usually due to mismatched keys or improper use of t…
75 …e on the <a href="authopt.html">Authentication Options</a> page. Common problems with configuratio…
82 …ages about configuration errors, name-lookup failures or initialization problems. Common system lo…
H A Dindex.html26 <li class="inline"><a href="#prob">Resolving Problems</a></li>
61 <h4 id="prob">Resolving Problems</h4>
62 …et life, NTP problems can be devilishly intricate. This distribution includes a number of utilitie…
63 …l">Hints and Kinks</a> pages contain useful information for identifying problems and devising solu…
H A Dbuild.html25 <li class="inline"><a href="#prob">If You Have Problems</a></li>
41 <h4 id="prob">If You Have Problems</h4>
42 …problems with your hardware and software environment (e.g. operating system-specific issues), brow…
/freebsd/contrib/ntp/sntp/m4/
H A Dsntp_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]
H A Dntp_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/crypto/openssl/doc/man3/
H A DDH_generate_parameters.pod67 The value of B<*codes> is updated with any problems found.
68 If B<*codes> is zero then no problems were found, otherwise the
96 value of B<*codes> is updated with any problems found. If B<*codes> is zero then
97 no problems were found, otherwise the following bits may be set:
/freebsd/contrib/ee/
H A DREADME.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/share/man/man3/
H A Dstats.3837 -EINVAL is returned if any problems are detected with the arguments.
869 EINVAL is returned if any problems are detected with the arguments.
878 return 0 on success, or EINVAL if any problems are detected with the arguments.
882 EINVAL is returned if any problems are detected with the arguments.
899 EINVAL is returned if any problems are detected with the arguments.
913 returns 0 on success, or EINVAL if any problems are detected with the arguments.
919 EINVAL is returned if any problems are detected with the arguments, otherwise
927 returns 0 on success, or EINVAL if any problems are detected with the arguments.
931 EINVAL is returned if any problems are detected with the arguments.
/freebsd/contrib/bzip2/
H A DREADME.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,
H A Dwords03 please read README.COMPILATION.PROBLEMS -- you might be able to
6 Also in README.COMPILATION.PROBLEMS are some hints that may help
/freebsd/contrib/kyua/admin/
H A Dcheck-api-docs.awk40 # Ignore known problems. As far as I can tell, all the cases listed here are
59 # Dump any other problems and account for the failure.
67 print "ERROR: Unexpected docstring problems encountered"
/freebsd/share/man/man4/
H A Dacpi.4143 Some systems need this help, others have display problems if it is enabled.
225 This can help diagnose suspend/resume problems.
267 This can fix some graphics cards that have problems such as LCD white-out
336 in case of problems.
420 may be causing problems, by listing the full path of the root of
581 or debug such problems.
640 IRQ routing problems.
/freebsd/contrib/nvi/cl/
H A DREADME.signal41 and obviously no reentrancy problems. The down side is that it's easy
55 2: Run in cbreak mode. There are two problems in this area. First, the
83 problems because it didn't use curses.) It entered signals following
124 There are a couple of other problems to consider.
141 Second, SIGTSTP has its own little problems. It's broadcast to the entire
/freebsd/sys/contrib/dev/athk/ath12k/
H A DKconfig24 If unsure, say Y to make it easier to debug problems. But if
33 If unsure, say Y to make it easier to debug problems. But if
/freebsd/sys/contrib/dev/athk/ath11k/
H A DKconfig36 If unsure, say Y to make it easier to debug problems.
44 If unsure, say Y to make it easier to debug problems.
/freebsd/tools/test/stress2/
H A DREADME1 stress2 is a tool for finding problems in the kernel.
10 stress2 has found a large number of problems:
/freebsd/secure/lib/libcrypto/man/man3/
H A DDH_generate_parameters.3206 The value of \fB*codes\fR is updated with any problems found.
207 If \fB*codes\fR is zero then no problems were found, otherwise the
227 value of \fB*codes\fR is updated with any problems found. If \fB*codes\fR is zero then
228 no problems were found, otherwise the following bits may be set:
/freebsd/contrib/netbsd-tests/lib/libc/regex/data/
H A Dregress.in1 # past problems, and suspected problems
/freebsd/sys/contrib/dev/rtw89/
H A DKconfig104 If unsure, say Y to simplify debug problems
113 If unsure, say Y to simplify debug problems
/freebsd/contrib/sendmail/
H A DREADME49 Sendmail often gets blamed for many problems that are actually the
50 result of other problems, such as overly permissive modes on directories.
192 errors due to nroff/groff problems. Known problems are:
314 problems.
381 | INTEROPERATION PROBLEMS |
412 authors if you have problems. (This directory is not

12345678910>>...54