Bug 1302718

Summary:	user 'tomcat': program '/bin/nologin' does not exist
Product:	[Fedora] Fedora	Reporter:	DaveG <daveg>
Component:	tomcat	Assignee:	Ivan Afonichev <ivan.afonichev>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	22	CC:	alee, coolsvap, csutherl, ivan.afonichev, java-sig-commits, krzysztof.daniel
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tomcat-7.0.68-3.fc22	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-25 22:22:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description DaveG 2016-01-28 12:56:47 UTC

Description of problem:

Minor niggle!

The tomcat UID specifies '/bin/nologin' as it's shell. That does not exist in a standard installation and should be '/sbin/nologin'.


Version-Release number of selected component (if applicable):

Historical through rawhide.


How reproducible:

Always.


Steps to Reproduce:
1. Install.
2. Run pwck.


Actual results:

user 'tomcat': program '/bin/nologin' does not exist


Expected results:

No errors or warnings.


Additional info:

http://pkgs.fedoraproject.org/cgit/rpms/tomcat.git/tree/tomcat.spec#n527

Comment 1 Coty Sutherland 2016-02-02 16:49:51 UTC

https://github.com/csutherl/fedora-tomcat/commit/44b6618

Comment 2 Fedora Update System 2016-02-23 10:05:10 UTC

tomcat-8.0.32-3.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-5e0bb2f21a

Comment 3 Fedora Update System 2016-02-23 17:35:52 UTC

tomcat-7.0.68-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-62619c1bda

Comment 4 Fedora Update System 2016-02-24 21:51:38 UTC

tomcat-8.0.32-3.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-5e0bb2f21a

Comment 5 Fedora Update System 2016-02-25 10:53:11 UTC

tomcat-7.0.68-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-62619c1bda

Comment 6 Fedora Update System 2016-02-27 15:43:29 UTC

tomcat-7.0.68-2.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-b19c75d748

Comment 7 Fedora Update System 2016-02-28 13:50:57 UTC

tomcat-7.0.68-2.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-b19c75d748

Comment 8 Fedora Update System 2016-03-11 06:49:17 UTC

tomcat-7.0.68-3.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-e6651efbaf

Comment 9 Fedora Update System 2016-03-12 16:53:24 UTC

tomcat-7.0.68-3.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-e6651efbaf

Comment 10 Fedora Update System 2016-03-25 22:21:30 UTC

tomcat-7.0.68-3.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.