Bug 688145

Summary: beah services: start rhts-compat from rc.local
Product: [Retired] Beaker Reporter: Marian Csontos <mcsontos>
Component: beahAssignee: beaker-dev-list
Status: CLOSED EOL QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 0.7CC: bpeck, mastyk, mcsontos, stl, tools-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: SimpleHarness, Triaged
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 679824 Environment:
Last Closed: 2020-02-11 12:18:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 679824    
Bug Blocks:    

Description Marian Csontos 2011-03-16 13:10:04 UTC
+++ This bug was initially created as a clone of Bug #679824 +++

rhts-compat service must start as the last one as it blocks.

Currently rc.local is not processed (which is compatible with rhts but it should be considered a bug.) while rhts-compat service is running.

Options:
- starting rhts-compat from rc.local only
- make rhts-compat non-blocking by starting in background

Comment 1 Bill Peck 2011-03-23 18:14:06 UTC
We ship screen with every release.  and I know screen can start services detached..

http://rpatterson.net/blog/screen-sessions-at-boot

Couldn't this replace the need for beah-rhts-compat service?

Comment 2 Marian Csontos 2011-03-24 07:39:45 UTC
I have used detached screen sessions in cases where dumb pty was not enough and I wanted to avoid compatible mode. In my case it was fine.

But I do not want more of those old-day compatibility issues.

Answer: may be.

Comment 3 Nick Coghlan 2012-10-17 04:38:12 UTC
Bulk reassignment of issues as Bill has moved to another team.

Comment 5 Martin Styk 2020-02-11 12:18:00 UTC
Beah is no longer supported by Beaker development team.
Instead of that, we are working on Restraint test harness. You can find all the features of Restraint here.

https://restraint.readthedocs.io/en/latest/

If you think your RFE should be still implemented as part of Restraint feel free to create a new BZ ticket.

https://bugzilla.redhat.com/enter_bug.cgi?product=Restraint

In case you have any question feel free to reach out to me
Thank you,
Martin Styk <martin.styk>