31b311af57
Red Hat's QA noticed that in case of the infamous "xattr>=0.4" error, swift-init exits with a zero error code, which confuses startup scripts (not Systemd though -- that one knows exactly if processes run or not). The easiest fix is to return the error code like Guido's blog post suggested. Change-Id: I7badd8742375a7cb2aa5606277316477b8083f8d Fixes: rhbz#1020480
28 lines
986 B
Python
Executable File
28 lines
986 B
Python
Executable File
#!/usr/bin/env python
|
|
# Copyright (c) 2010-2012 OpenStack Foundation
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
# you may not use this file except in compliance with the License.
|
|
# You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
# implied.
|
|
# See the License for the specific language governing permissions and
|
|
# limitations under the License.
|
|
|
|
import sys
|
|
from swift.common.utils import parse_options
|
|
from swift.common.wsgi import run_wsgi
|
|
from swift.obj import server
|
|
|
|
|
|
if __name__ == '__main__':
|
|
conf_file, options = parse_options()
|
|
sys.exit(run_wsgi(conf_file, 'object-server', default_port=6000,
|
|
global_conf_callback=server.global_conf_callback,
|
|
**options))
|