Op 23 apr. 2013, om 23:03 heeft George McCollister
george.mccollis...@gmail.com het volgende geschreven:
On 04/20/2013 08:04 AM, Koen Kooi wrote:
Op 18 apr. 2013, om 19:18 heeft George
McCollistergeorge.mccollis...@gmail.com het volgende geschreven:
On 04/10/2013 12:03 PM, Koen Kooi
On 04/20/2013 08:04 AM, Koen Kooi wrote:
Op 18 apr. 2013, om 19:18 heeft George
McCollistergeorge.mccollis...@gmail.com het volgende geschreven:
On 04/10/2013 12:03 PM, Koen Kooi wrote:
Hi,
I have a bit of a heisenbug where dropbear.socket will just die and needs a
systemctl restart
Op 18 apr. 2013, om 19:18 heeft George McCollister
george.mccollis...@gmail.com het volgende geschreven:
On 04/10/2013 12:03 PM, Koen Kooi wrote:
Hi,
I have a bit of a heisenbug where dropbear.socket will just die and needs a
systemctl restart dropbear.socket. I can't tell why it's
Am 18.04.2013 16:44, schrieb Lennart Poettering:
On Thu, 18.04.13 16:38, Thomas Bächler (tho...@archlinux.org) wrote:
Am 18.04.2013 16:04, schrieb Lennart Poettering:
That said, screen should probably set up a new PAM session of its own
and detach from the original one.
That sounds like a
Op 17 apr. 2013, om 21:05 heeft Lennart Poettering lenn...@poettering.net het
volgende geschreven:
On Wed, 10.04.13 19:03, Koen Kooi (k...@dominion.thruhere.net) wrote:
Hi,
I have a bit of a heisenbug where dropbear.socket will just die and
needs a systemctl restart dropbear.socket. I
On Thu, 18.04.13 09:28, Koen Kooi (k...@dominion.thruhere.net) wrote:
And if the somebody invokes shutdown() on the listening socket (not the
connection socket), but that's a really weird thing to do. But people do
weird things, and this has occured before.
Otherwise I have no idea
Am 18.04.2013 16:04, schrieb Lennart Poettering:
That said, screen should probably set up a new PAM session of its own
and detach from the original one.
That sounds like a good idea - unfortunately, screen does not seem to
have PAM session support at all, and I couldn't find the obvious place
On Thu, 18.04.13 16:38, Thomas Bächler (tho...@archlinux.org) wrote:
Am 18.04.2013 16:04, schrieb Lennart Poettering:
That said, screen should probably set up a new PAM session of its own
and detach from the original one.
That sounds like a good idea - unfortunately, screen does not seem
On 04/10/2013 12:03 PM, Koen Kooi wrote:
Hi,
I have a bit of a heisenbug where dropbear.socket will just die and needs a
systemctl restart dropbear.socket. I can't tell why it's dying, just that it
does within 3 days of uptime. After restarting it it seems to be rock solid
again for at least
On Wed, 10.04.13 19:03, Koen Kooi (k...@dominion.thruhere.net) wrote:
Hi,
I have a bit of a heisenbug where dropbear.socket will just die and
needs a systemctl restart dropbear.socket. I can't tell why it's
dying, just that it does within 3 days of uptime. After restarting it
it seems to
Op 11 apr. 2013, om 21:09 heeft David Strauss da...@davidstrauss.net het
volgende geschreven:
On Wed, Apr 10, 2013 at 11:00 PM, Koen Kooi k...@dominion.thruhere.net
wrote:
restarting it once it fails
Is it the socket or the service?
socket
___
2013/4/11 Koen Kooi k...@dominion.thruhere.net:
On Wed, Apr 10, 2013 at 11:00 PM, Koen Kooi k...@dominion.thruhere.net
wrote:
restarting it once it fails
Is it the socket or the service?
socket
I believe I experienced this with PHP-FPM when I injected the sockets
by abusing PHP-FPM's
Op 10 apr. 2013, om 22:20 heeft Kok, Auke-jan H auke-jan.h@intel.com
het volgende geschreven:
On Wed, Apr 10, 2013 at 1:12 PM, David Strauss da...@davidstrauss.net wrote:
Are you sure it's not the corresponding service that really failed?
actually, that's a good point, but if the
On Wed, Apr 10, 2013 at 11:00 PM, Koen Kooi k...@dominion.thruhere.net wrote:
restarting it once it fails
Is it the socket or the service?
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [mobile]
___
systemd-devel mailing list
On 04/10/2013 05:03 PM, Koen Kooi wrote:
Hi,
I have a bit of a heisenbug where dropbear.socket will just die and needs a
systemctl restart dropbear.socket. I can't tell why it's dying, just that it
does within 3 days of uptime. After restarting it it seems to be rock solid
again for at least
On Wed, Apr 10, 2013 at 8:03 PM, Koen Kooi k...@dominion.thruhere.net wrote:
Hi,
I have a bit of a heisenbug where dropbear.socket will just die and needs a
systemctl restart dropbear.socket. I can't tell why it's dying, just that it
does within 3 days of uptime. After restarting it it
Op 10 apr. 2013, om 19:13 heeft Mantas Mikulėnas graw...@gmail.com het
volgende geschreven:
On Wed, Apr 10, 2013 at 8:03 PM, Koen Kooi k...@dominion.thruhere.net wrote:
Hi,
I have a bit of a heisenbug where dropbear.socket will just die and needs a
systemctl restart dropbear.socket. I
On Wed, Apr 10, 2013 at 11:10 AM, Koen Kooi k...@dominion.thruhere.net wrote:
Op 10 apr. 2013, om 19:13 heeft Mantas Mikulėnas graw...@gmail.com het
volgende geschreven:
On Wed, Apr 10, 2013 at 8:03 PM, Koen Kooi k...@dominion.thruhere.net
wrote:
Hi,
I have a bit of a heisenbug where
Are you sure it's not the corresponding service that really failed?
On Wed, Apr 10, 2013 at 11:46 AM, Kok, Auke-jan H
auke-jan.h@intel.com wrote:
On Wed, Apr 10, 2013 at 11:10 AM, Koen Kooi k...@dominion.thruhere.net
wrote:
Op 10 apr. 2013, om 19:13 heeft Mantas Mikulėnas
On Wed, Apr 10, 2013 at 1:12 PM, David Strauss da...@davidstrauss.net wrote:
Are you sure it's not the corresponding service that really failed?
actually, that's a good point, but if the socket unit is dead, I
assume that systemd no longer is bind()ed to the ports...
Koen, can you verify that
On Wed, Apr 10, 2013 at 1:20 PM, Kok, Auke-jan H
auke-jan.h@intel.com wrote:
actually, that's a good point, but if the socket unit is dead, I
assume that systemd no longer is bind()ed to the ports...
I'd have to look at source or run some experiments for details, but I
know systemd's socket
21 matches
Mail list logo
