On Wed, 2011-08-31 at 17:55 +0200, Lennart Poettering wrote:
On Wed, 31.08.11 17:01, Nils Philippsen (n...@redhat.com) wrote:
What's missing is a way to enable/disable/monitor enablement of a
systemd/SysV service, partly because systemd doesn't expose this via its
dbus interface (which
On Thu, 2011-09-01 at 13:57 +0200, Lennart Poettering wrote:
On Thu, 01.09.11 13:49, Nils Philippsen (n...@redhat.com) wrote:
We actually support this for quite some time now in F16. You can get a
list of all unit files that are installed with their enablement status,
and you get
On Thu, 2011-09-01 at 15:28 +0200, Lennart Poettering wrote:
On Thu, 01.09.11 15:13, Nils Philippsen (n...@redhat.com) wrote:
On Thu, 2011-09-01 at 13:57 +0200, Lennart Poettering wrote:
On Thu, 01.09.11 13:49, Nils Philippsen (n...@redhat.com) wrote:
We actually support this for
On Mon, 2011-08-29 at 20:20 -0700, Adam Williamson wrote:
On Sun, 2011-08-28 at 22:48 -0600, Peter G. wrote:
In the system-config-services, I see that sshd is not running when I boot
the
computer.
You can't rely on system-config-services any more, as it does not
understand systemd
On Wed, 2011-08-31 at 17:01 +0200, Nils Philippsen wrote:
On Mon, 2011-08-29 at 20:20 -0700, Adam Williamson wrote:
On Sun, 2011-08-28 at 22:48 -0600, Peter G. wrote:
In the system-config-services, I see that sshd is not running when I boot
the
computer.
You can't rely on
On Tue, 2011-08-30 at 22:06 -0600, Peter G. wrote:
I am looking forward to the day when systemd becomes smart enough to know
that
it should start the required service for me.
systemd is already smart enough, but the services themselves have to be
written with support, and sometimes the
Dne 31.8.2011 18:39, Adam Williamson napsal(a):
systemd is already smart enough, but the services themselves have to be
written with support, and sometimes the underlying daemons need slight
tweaking to support socket activation.
Just a bit of self-promotion. Bitlbee in Fedora has socket
Adam Williamson wrote:
'systemctl status sshd.service' will tell you about the service: it
should say 'active (running)'. 'failed' or 'active (exited)' would be
bad.
This is the command I have been relying on.
1. systemd will automatically recognize that I need sshd.service to be
started
On Sun, 2011-08-28 at 22:48 -0600, Peter G. wrote:
In the system-config-services, I see that sshd is not running when I boot the
computer.
You can't rely on system-config-services any more, as it does not
understand systemd native services.
For a basic check, just do 'ps aux | grep sshd',
In the system-config-services, I see that sshd is not running when I boot the
computer.
The message at the top right says that:
The sshd service is managed by systemd. It may be started then run in the
background, or be activated on demand...
I am unclear about the be activated on demand
10 matches
Mail list logo
