Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Diagnostic page feature #33

Closed
GoogleCodeExporter opened this issue Jul 29, 2015 · 8 comments
Closed

Diagnostic page feature #33

GoogleCodeExporter opened this issue Jul 29, 2015 · 8 comments

Comments

@GoogleCodeExporter
Copy link

Add a diagnostic page. 

This page should check domus installation :
* check heyu base
* x10.sched file writable
* heyuexec is executable
* heyu is running 

Original issue reported on code.google.com by philippe...@gmail.com on 14 Apr 2010 at 8:30

@GoogleCodeExporter
Copy link
Author

I like this. Getting domusLink up and running on my NAS appliance was a pain....

Original comment by brandtda...@gmail.com on 14 Apr 2010 at 11:58

@GoogleCodeExporter
Copy link
Author

Also, this page should be able to take care of the 'Heyu cleanup' section in 
the man
page.

That is; heyu stop, killall heyu, rm lock files, rm spool files, heyu start

Original comment by brandtda...@gmail.com on 14 Apr 2010 at 11:59

@GoogleCodeExporter
Copy link
Author

The first check that domus makes when it is executed it a subset of these 
items. The
goal is then to expand the checks and show more status.

The cleanup Brandt is asking could be something to add to the utility page as it
would be after the system is setup properly and running.

Make sense?

Original comment by bwsamuels@gmail.com on 15 Apr 2010 at 2:41

@GoogleCodeExporter
Copy link
Author

On my NAS, I also have to make a couple changes to php.ini....open_basedir and 
exec
paths..

If heyu is not running I think it should check for LCK files at least and warn 
the
user that heyu was improperly shut down, if not take care of it automatically...

Original comment by brandtda...@gmail.com on 15 Apr 2010 at 6:07

@GoogleCodeExporter
Copy link
Author

Original comment by bwsamuels@gmail.com on 15 May 2010 at 2:54

  • Changed state: Accepted
  • Added labels: Milestone-v1.2

@GoogleCodeExporter
Copy link
Author

Original comment by bwsamuels@gmail.com on 20 May 2010 at 1:02

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

check perms on TTY and TTY_AUX devices

Original comment by brandtda...@gmail.com on 20 May 2010 at 3:20

@GoogleCodeExporter
Copy link
Author

This issue was closed by revision r768.

Original comment by bwsamuels@gmail.com on 4 Jun 2010 at 12:51

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant