Home
last modified time | relevance | path

Searched hist:"6 a3d55f9" (Results 1 – 25 of 26) sorted by relevance

12

/openbsd/usr.sbin/lpd/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/radiusd/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/iscsictl/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/npppd/npppd/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/ldomctl/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/eigrpd/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/ypldap/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/dvmrpd/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/acme-client/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/ldapd/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/ripd/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/ifstated/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/ospf6d/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/hostapd/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/ntpd/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/ldpd/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/vmd/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/ospfd/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/snmpd/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/httpd/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/sbin/iked/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/sbin/ipsecctl/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/relayd/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/usr.sbin/smtpd/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@
/openbsd/sbin/pfctl/
H A Dparse.y6a3d55f9 Mon Jul 09 12:05:10 GMT 2018 krw <krw@openbsd.org> No need to mention which memory allocation entry point failed (malloc,
calloc or strdup), we just need to log that we ran out of memory in a
particular function.

Recommended by florian@ and deraadt@

ok benno@ henning@ tb@

12