Re: gnome keyring daemon from cron job

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2009/4/20 Christoph Höger <choeger@xxxxxxxxxxxxxxx>:
>
> I could fix that by adding DBUS_SESSION_BUS_ADDRESS=autolaunch: to the
> cron job. That made gnomekeyring reachable again.

If you have an existing desktop session though that will cause things
to break most likely though, since you can now get two
gnome-keyring-daemon instances both of which are accessing the single
keyring file.  If you're not logged in though that works.

Aside from patching cron we should really ship a "ck-run-in-desktop"
command with ConsoleKit, it wouldn't be difficult to write.

> Is there something wrong with .dbus/session/* stuff?

The pitfall with putting stuff in $HOME that's per-user-per-machine is
that it hard-breaks in NFS scenarios.  We could put the dbus machine
uuid (or smolt uuid) in the filename, but I think using ConsoleKit is
cleaner.

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux