security policies? - Re: New DiskMonitoring package

[Carl Karsten]

Brian Sutherland wrote:
> Thanks Carl,
> 
> On Tue, Apr 05, 2005 at 07:40:52AM -0500, Carl Karsten wrote:
> 
>>root at curb:~ # /etc/init.d/smartmontools start
>>
>>(no output?)
> 
> 
> You should check /etc/default/smartmontools to make sure the daemon
> starts by default.
> 

root at curb:~ # vi /etc/default/smartmontools
...
# uncomment to start smartd on system startup
# start_smartd=yes
...
(uncommented, write, save.)

root at curb:~ # /etc/init.d/smartmontools start
  * Starting S.M.A.R.T. daemon... 
   [ ok ]


> 
>>root at curb:~ # DISPLAY=:0.0 smart-notifier
> 
>   ^^^^
> 
>>Traceback (most recent call last):
>>   File "/usr/bin/smart-notifier", line 11, in ?
>>     smart_notifier.service()
>>   File "/usr/share/smart-notifier/smart_notifier/__init__.py", line 72, 
>>in service
>>     bus=dbus.SystemBus())
>>   File "/usr/lib/python2.4/site-packages/dbus.py", line 244, in __init__
>>     dbus_bindings.bus_acquire_service(self._bus.get_connection(), 
>>service_name)
>>   File "dbus_bindings.pyx", line 1489, in dbus_bindings.bus_acquire_service
>>dbus_bindings.DBusException: Connection ":1.5" is not allowed to own the 
>>service "smart_notifier.DbusService" due to security policies in the 
>>configuration file
> 
> 
> Here is a problem, smart-notifier should be run by the user. (I really
> should get this to work by default.)
> 
> also a "/etc/init.d/dbus-1 restart" before trying anything is a ggod
> idea(another thing that should be done automatically).
> 


root at curb:~ # /etc/init.d/dbus-1 restart
  * Stopping Hardware abstraction layer: 
   [ ok ]
  * Stopping system message bus: 
   [ ok ]
  * Starting system message bus: 
   [ ok ]
  * Starting Hardware abstraction layer: 
   [ ok ]

juser at curb:~$ DISPLAY=:0.0 smart-notifier

Off it goes till I hit ^C.  should I see anything, like a "I am running" 
icon up by the clock?

Other than hittig the drive with a hammer, is there some way to generate 
some signals?

Carl K