Michal Schmidt wrote:
On 03/05/2013 04:02 AM, David Highley wrote:
Unlike the bug report which indicates you can to a sync reboot,
nothing but the power switch gets this system out of the issue.
Did you use the -f switch?
sync reboot -f
Missed the the -f switch. Will give it a try
We are attempting to create systemd files for an ssh port monitoring
process. When we enable and attempt to start the service we get multiple
executions of the daemon and systemctl does not return until we do a
control-c. The init script and our attempt at replacement:
#!/bin/bash
#
# chkconfig:
Twice now we have one Fedora 18 system where systemd seems to get into a
non responsive state. We are not able to get the status of any service
and we're not able to do an init 6 to restart the system.
Did notice today that a full process list showed a message about abrt
and something to the
Lennart Poettering wrote:
On Mon, 04.03.13 07:56, David Highley (dhigh...@highley-recommended.com)
wrote:
Twice now we have one Fedora 18 system where systemd seems to get into a
non responsive state. We are not able to get the status of any service
and we're not able to do an init 6
David Highley wrote:
Lennart Poettering wrote:
On Mon, 04.03.13 07:56, David Highley (dhigh...@highley-recommended.com)
wrote:
Twice now we have one Fedora 18 system where systemd seems to get into a
non responsive state. We are not able to get the status of any service
Lennart Poettering wrote:
On Mon, 04.03.13 10:24, David Highley (dhigh...@highley-recommended.com)
wrote:
Lennart Poettering wrote:
On Mon, 04.03.13 07:56, David Highley (dhigh...@highley-recommended.com)
wrote:
Twice now we have one Fedora 18 system where systemd seems
What to express that firewalld is not ready to be the default firewall.
We believe it is a step in the right direction, but lacks documentation,
migration support, and the crucial need for permanent use of direct
rules on restart.
We did attempt to put into the Fedora distribution the sshdfilter
