On Fri, 10 Jun 2011 18:42:11 +0200 Denys Vlasenko wrote: > On Fri, 2011-06-10 at 15:36 +0200, Michal Schmidt wrote: > > > Why does systemd link against libpam? > > > systemd does logins now, not /bin/login or gdm or ...? > > > > to implement PAMName= (man systemd.exec) > > I don't see any users of this feature on my F15. > I searched with Google and come up empty too. > > But anyway, assuming it's a useful feature, why it has to be done by > systemd? A nice property of systemd is that it takes care of setting up the environment for each service. PAMName can be considered one of the pieces of the environment. It is expected that services will eventually start taking advantage of it and cease to implement these things themselves. It makes them simpler. See http://0pointer.de/public/systemd-man/daemon.html for how "new-style" daemons are made simpler. > > > libwrap? systemd is a network application now too? > > > > to implement TCPWrapName= (man systemd.exec) > > Again, why it has to be done *by systemd*? As systemd takes away the responsibility of creating sockets from the services when it offers socket activation, it makes sense to offer the option to filter the activation requests using libwrap. Michal -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
