Default services enabled

[Tomasz Torcz]

On Fri, Aug 19, 2011 at 11:07:45AM -0400, Steve Grubb wrote:
> On Friday, August 19, 2011 10:38:59 AM Ola Thoresen wrote:
> > On 19. aug. 2011 16:00, "Jóhann B. Guðmundsson" wrote:
> > > On 08/19/2011 12:35 PM, Steve Grubb wrote:
> > >> On Friday, August 19, 2011 03:41:33 AM Tim Waugh wrote:
> > >>> On Thu, 2011-08-18 at 16:52 -0600, Orion Poplawski wrote:
> > >>>> It's not so much cups start up being slow as discovering network
> > >>>> printers. That can take up to a minute I think.
> > >>> 
> > >>> This is true... however, discovered printers are cached so this is only
> > >>> an issue the first time CUPS starts after installation (or after
> > >>> connection to a new network).
> > >> 
> > >> If CUPS is enabled by default, can this be done for runlevel 5 only? It
> > >> should not be enabled by default for servers.
> > > 
> > > There are no such things as run levels in systemd but yeah desktop
> > > related services should just be enabled when booting into the graphical
> > > target.
> > 
> > Just a thought - would it make sense to create a "server-target" (and/or
> > "desktop-target") that is independent of graphical-target?
> 
> I would hope there are pre-canned targets for different crowds. I also hope there is a 
> secure default configuration for each of them. I also hope there is a way to list all 

  There was some talk about ”preset” - what should be enabled in various scenarios (spins).

> of these targets and what is enabled for each one, because that will be needed for any 
> kind of security analysis.

  System settings:
% ls /lib/systemd/system/<name>.target.wants/
  Admin settings:
% ls /etc/systemd/system/<name>.target.wants/

-- 
Tomasz Torcz                 "God, root, what's the difference?"
xmpp: zdzichubg at chrome.pl         "God is more forgiving."