WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki
« previous next »
Pages: 1 [2]   Go Down

Author Topic: Adverse Effect of Change to dbus Extention  (Read 5784 times)

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 14815
Re: Adverse Effect of Change to dbus Extention
« Reply #15 on: February 07, 2010, 09:30:31 AM »
Quote from: Jason W on February 07, 2010, 08:59:32 AM
Since the list is large, perhaps we could add the machine-id commands to the dbus.tcz startup script to save a lot of trouble.  That way dbus info is there to satisfy many extensions, and save the need to add these lines to all the other startup scripts. 

I could certainly do that - let's leave this overnight for comments before I go ahead
Logged

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: Adverse Effect of Change to dbus Extention
« Reply #16 on: February 08, 2010, 02:01:43 AM »
I have added the machine-id to dbus startup script.
Logged
10+ Years Contributing to Linux Open Source Projects.

Offline Jason W

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 9730
Re: Adverse Effect of Change to dbus Extention
« Reply #17 on: February 08, 2010, 06:07:53 AM »
Thanks, now I will test that list and identify which of them may actually need dbus running to work.
Logged

Offline Jason W

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 9730
Re: Adverse Effect of Change to dbus Extention
« Reply #18 on: February 08, 2010, 12:19:20 PM »
I have tested some of the end use apps in the before mentioned list, and they seem to be either happy with only the dbus machine-id info available, or they or their dependencies start dbus if needed.

If there are any extensions that are not happy with the current setup, and need dbus started manually, then list them here and they will be fixed.
Logged
Pages: 1 [2]   Go Up
« previous next »