Searched refs:certainly (Results 1 – 14 of 14) sorted by relevance
1411 int32_t certainly[lastdb]; in restart() local1417 certainly[cnt] = dbs[cnt].head->nscd_certainly_running; in restart()1463 dbs[cnt].head->nscd_certainly_running = certainly[cnt]; in restart()
61 For such a common format (@math{=} character set) eight bits are certainly974 most unusual thing about this piece of code certainly is the duplication980 There are certainly many more and even better solutions to this problem.1836 return with an error immediately. This certainly is not the most2017 sets in use, it is certainly not practical to encode the conversions2131 last section it is certainly good to note that the implementation in
745 There are probably bugs in @theglibc{}. There are certainly
1890 are certainly not safe to use in a signal handler.1981 safe in this program because it is certainly not being called outside2776 that signal is not blocked is almost certainly bad design.
217 programs is certainly @code{mount}(8). The @code{-o} option take one
12 certainly not a good solution since extending the set of languages is
2702 from modifying these strings. Modifying the strings will almost certainly
3694 % after the title page, which we certainly don't want.6723 % We'll almost certainly start a paragraph next, so don't let that
3656 is almost certainly incorrect, because the signal could happen at any
1087 certainly leave the other independent channels positioned somewhere
3790 whitespace character appears. This almost certainly means that invalid
682 There are probably bugs in the GNU C Library. There are certainly
828 # I can certainly confirm for my part that Daylight Saving in NSW did in fact
1379 these are things that must most certainly be studied.