为什么不是sidekiq守护进程？

Question

生病sidekiq的后牙：

# sidekiq -C config.yml 
--- 
:verbose: false 
:daemonize: true 
:pidfile: ./tmp/pids/sidekiq.pid 
:logfile: ./log/sidekiq.log 
:concurrency: 25 
# Set timeout to 8 on Heroku, longer if you manage your own systems. 
:timeout: 30 
:queues: 
    - [often, 7] 
    - [default, 5] 
    - [seldom, 3] 

我跑

sidekiq -C config/sidekiq.yml 
     s 
     ss 
    sss sss   ss 
    s sss s ssss sss ____ _  _  _ _ 
    s  sssss ssss /___|(_) __| | ___| | _(_) __ _ 
    s   sss   \___ \| |/ _` |/ _ \ |//|/ _` | 
    s sssss s    ___) | | (_| | __/ <| | (_| | 
    ss s s   |____/|_|\__,_|\___|_|\_\_|\__, | 
    s  s s           |_| 
     s s 
     sss 
     sss 

，并没有守护进程。它只是挂在那里。但是，它会记录到指定的日志文件并创建一个pid。

这里是我的日志：

2014-05-08T11:13:58Z 12036 TID-9g3gg INFO: Running in ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-linux] 
2014-05-08T11:13:58Z 12036 TID-9g3gg INFO: See LICENSE and the LGPL-3.0 for licensing details. 
2014-05-08T11:13:58Z 12036 TID-9g3gg INFO: Starting processing, hit Ctrl-C to stop 
2014-05-08T11:13:58Z 12036 TID-y7cwk INFO: Booting Sidekiq 3.0.1 with redis options {} 

我认为这是进程化。但是，它不会让我回到命令行？

Answer 1

选项是daemon，而不是守护进程。