nt release (added unconditionally in 1.0.1g, turned into option in
1.0.1h) [1].
[1]
http://git.openssl.org/gitweb/?p=openssl.git;a=commit;h=aaed77c55ecf82594bf3b44b1bcad66c42611777
Best regards,
Piotr Sikora
quot;no-xxx".
However, some functions aren't really "features", for example
X509_check_host() from OpenSSL-1.0.2, and OPENSSL_VERSION_NUMBER check is
the only reliable way to test for it... That is, unless you're compiling
against LibreSSL :(
Best regards,
Piotr Sikora
ON_NUMBER >= 0x20001000L
instead of just breaking build, like it's happening right now.
Best regards,
Piotr Sikora
&& !defined LIBRESSL_VERSION_NUMBER
...
#endif
in order to compile with LibreSSL, for no good reason.
Best regards,
Piotr Sikora
applications that already support
features from OpenSSL-1.0.2 and/or OpenSSL-1.1.0 won't compile against
LibreSSL, because they see version 2.0.0, not 1.0.1 (which LibreSSL was
forked off).
Best regards,
Piotr Sikora
Hello,
it seems that setlogin and name weren't replaced everywhere.
I also replaced ".Nm" with ".Fn getentropy" to get the ().
Best regards,
Piotr Sikora
--- lib/libc/sys/getentropy.2-orig Fri Jun 13 10:13:05 2014
+++ lib/libc/sys/getentropy.2 Fri Jun 13 10:20
s "hard to use" for files as the kqueue() interface is for
networking stuff.
It would be definitely nice to have those, especially since pretty much
everyone else (NetBSD, FreeBSD, DragonFly, Solaris, MacOSX, Linux) is
already providing them.
Best regards,
Piotr Sikora < piotr.sik...@frickle.com >
nly "foobar(failed)"? By definition, it would be printed
only for ports with custom rc_reload logic.
Best regards,
Piotr Sikora < piotr.sik...@frickle.com >
Index: rc.subr
===
RCS file: /cvs/src/etc/rc.d/rc.subr,v
retriev
t;
command even if foo daemon fails to start later in the process (ports
already in use, etc).
What about custom RC_RELOAD_OUTPUT variable that would print result for
ports with custom logic? Would that work for you?
Best regards,
Piotr Sikora < piotr.sik...@frickle.com >
do* return correct exit value in case of success / error, which
means that returning "daemon(ok/failed)" in their case is useful.
Best regards,
Piotr Sikora < piotr.sik...@frickle.com >
xt best thing we can do to
inform users that command did or did not succeed.
Because it is next to impossible to get a correct return. By default,
all we can check is that SIGHUP was successfull or not, that's it.
Yes, but there are 8 ports that have custom rc_reload logic.
Best regards,
Piotr Sikora < piotr.sik...@frickle.com >
le would assume that nginx reloaded
successfully.
Granted, there are only 8 ports with custom rc_reload logic, but why should
they suffer?
Best regards,
Piotr Sikora < piotr.sik...@frickle.com >
Hi,
No, this was left out on purpose. If you want to see stderr, use
RC_DEBUG.
But this patch doesn't bring back stderr, it just prints
"daemon(ok/failed)".
This is already present in "start", "restart" and "stop" commands, why
should &qu
Hello,
attached patch adds "daemon(ok/failed)" output to the "reload" command.
I believe it's extremely useful, since daemon's stderr is suppressed
by rc_do.
Best regards,
Piotr Sikora < piotr.si
Hey,
Insufficient for the daemon_flags=-n case. To be completely safe, use
printf:
daemon_flags=$(printf '%s\n' "${daemon_flags}" | tr -s "[:space:]")
It's indeed better / safer solution, thanks!
Best regards,
Piotr Sikora < piotr.sik...@frickle.com >
echo "-n"
still echoes nothing. Or am I missing something?
Damn, how did I miss that? I was pretty sure that I've checked passing just
"-n" prior to submitting this, but apparently I didn't.
Thanks.
Best regards,
Piotr Sikora < piotr.sik...@frickle.com >
Hello,
$daemon_flags are sanitized using echo and tr, but the input isn't quoted,
which makes it indistinguishable from echo's options. Effect of this is that
when $daemon_flags starts with "-n" then this argument is lost in the
process.
Best regards,
Piotr Sikora < p
17 matches
Mail list logo
