Ticket #659 (closed enhancement: fixed)

Opened 10 years ago

Last modified 10 years ago

Make the output produced by the stop_seattle and uninstall scripts more base-user friendly

Reported by: zackrb Owned by: zackrb
Priority: minor Milestone:
Component: installer Version: 0.1l
Severity: Medium Keywords:
Cc: Blocking:
Blocked By:

Description

Many users may not know what a lock is, for example. Printing this information is only confusing for them and also not really helpful for more advanced users either.

Change History

Changed 10 years ago by zackrb

The output is now user friendly; however, the output needs to be generated by the stop_seattle.sh shell script that calls impose_seattlestopper_lock.py once the seattlestopper_lock has been made obsolete.

Explained: Because impose_seattlestopper_lock.py kills nmmain.py and softwareupdater.py, but runs forever and thus must be detached from the shell, a race condition occurs when stop_seattle.sh tries to check to see if impose_seattlestopper_lock.py already stopped nmmain.py and softwareupdater.py. Once the seattlestopper lock is made obsolete, the python program that kills nmmain.py and softwareupdater.py will not have to be detached from the shell, thus solving the race condition problem because the python program will have terminated by the time the shell script tries to find out whether or not it completed it's task of killing nmmain.py and softwareupdater.py

Changed 10 years ago by zackrb

This ticket cannot complete until ticket #721 has been closed.

Changed 10 years ago by zackrb

The seattlestopper_lock has been removed now that crontab will no longer try and start seattle every minute. See r3322. The only thing remaining is to add the functionality to stop_seattle.sh to confirm that nmmain.py and softwareupdater.py have been stopped before telling the user this has happened.

Changed 10 years ago by zackrb

  • status changed from new to closed
  • resolution set to fixed

Fixed in r3324

Note: See TracTickets for help on using tickets.