Re: [gentoo-user] systemd-197-r1 starts gdm-3.6.2

[Canek Peláez Valdés]

On Thu, Jan 31, 2013 at 5:27 PM, Alecks Gates <alecks.g@×××××.com> wrote:
> On Wed, Jan 30, 2013 at 11:35 PM, Canek Peláez Valdés <caneko@×××××.com> wrote:
>> On Wed, Jan 30, 2013 at 3:14 PM, Alecks Gates <alecks.g@×××××.com> wrote:
>>> On Wed, Jan 30, 2013 at 2:22 PM, Stefan G. Weichinger <lists@×××××.at> wrote:
> [snip]
>>>
>>> I switched to systemd not too long ago and I have the same issue as
>>> well, at least it sounds the same -- Basically, I get a hanging GDM
>>> after typing my password and logging in.  I'm certainly no expert, but
>>> I've enjoyed the rest of systemd so I've stuck with it and just use
>>> startx to boot into Gnome3.  I'll attatch some logs from /var/log/gdm.
>>
>> Alecks, your error is different, and one similar to one I had before:
>>
>> https://bugs.gentoo.org/show_bug.cgi?id=363061
>>
>> What does systemctl status accounts-daemon.service says? Actually,
>> could tell me what services are in red when you run "systemctl --full
>> --all"?
>>
>> Regards.
>> --
>> Canek Peláez Valdés
>> Posgrado en Ciencia e Ingeniería de la Computación
>> Universidad Nacional Autónoma de México
>>
>
> $ systemctl status accounts-daemon.service
> accounts-daemon.service - Accounts Service
>           Loaded: loaded (/usr/lib64/systemd/system/accounts-daemon.service; disabled)
>           Active: active (running) since Thu 2013-01-31 17:02:33 CST; 16min ago
>         Main PID: 3326 (accounts-daemon)
>           CGroup: name=systemd:/system/accounts-daemon.service
>                   └─3326 /usr/libexec/accounts-daemon
>
> $ systemctl --full --all | grep error
> auditd.service   error  inactive dead      auditd.service
> plymouth-quit-wait.service   error  inactive dead
> plymouth-quit-wait.service
> plymouth-start.service   error  inactive dead      plymouth-start.service
> syslog.service   error  inactive dead      syslog.service
>
>
> A couple days ago (after reading your email from another topic) I
> noticed plymouth services do not exist on my machine, and checked
> where it's supposed to come from:
> $ e-file plymouth-start.service
> [I] sys-apps/systemd
>         Available Versions:     44-r1 44
>         Last Installed Ver:     197-r1(Mon 28 Jan 2013 03:58:41 PM CST)
>         Homepage:               http://www.freedesktop.org/wiki/Software/systemd
>         Description:            System and service manager for Linux
>         Matched Files:          /usr/lib/systemd/system/sysinit.target.wants/plymouth-start.service;
> /usr/lib/systemd/system/plymouth-start.service;
> $ e-file plymouth-quit-wait.service
> [I] sys-apps/systemd
>         Available Versions:     44 44-r1
>         Last Installed Ver:     197-r1(Mon 28 Jan 2013 03:58:41 PM CST)
>         Homepage:               http://www.freedesktop.org/wiki/Software/systemd
>         Description:            System and service manager for Linux
>         Matched Files:          /usr/lib/systemd/system/multi-user.target.wants/plymouth-quit-wait.service;
> /usr/lib/systemd/system/plymouth-quit-wait.service;
>
> And auditd.service isn't found in e-file at all.  Normally I'm not
> surprised by a lack of .service files, as it's not a huge issue[1],
> but if this one's so important, where is it?
>
> Canek, I'm getting the feeling your systemd install has matured over
> the years, at least with regard to unit files.

Not really; at some point yes, but I believe I run a pretty much
out-of-the-box systemd. As I explained to Stefan a couple of mails
before, you can mask the unit files you don't have, by linking them in
/etc/systemd/system. That's all I do, and only with syslog and
rc-local:

# ls -l /etc/systemd/system/|grep /dev/null
lrwxrwxrwx 1 root root    9 Aug 16 13:51 rc-local.service -> /dev/null
lrwxrwxrwx 1 root root    9 Aug 16 13:49 syslog.service -> /dev/null

Besides that I have a vixie-cron.service, and that's all the
customization I do. Everything else is as defined by the respective
upstream developers. In my media center I have a couple more of custom
unit files.

> [1] Unit files are surprisingly easy for me to create -- I always
> found a barrier to entry with init scripts.

I didn't have any problem writing init scripts, but I agree unit files
are really easy.

Regards.
-- 
Canek Peláez Valdés
Posgrado en Ciencia e Ingeniería de la Computación
Universidad Nacional Autónoma de México