> -----Original Message----- > From: users-bounces@xxxxxxxxxxxxxxxxxxxxxxx > [mailto:users-bounces@xxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of > T.C. Hollingsworth > Sent: Tuesday, November 01, 2011 21:07 > To: Community support for Fedora users > Subject: Re: my SysV daemons not starting on boot > > On Tue, Nov 1, 2011 at 5:01 PM, Michael D. Berger > <m.d.berger@xxxxxxxx> wrote: > > Always, started or not, I get the same thing: > > > > #systemctl status myDaemon.service > > myDaemon.service > > Loaded: error > > Active: inactive (dead) > > That's very strange. If a file "/etc/init.d/myDaemon" > exists, systemd should create a virtual "myDaemon.service". > (Emphasis on "virtual"; no file is created on disk.) > > Check syslog (/var/log/messages) for any errors related to > your daemon. If there are none, reboot and edit your kernel > command line, removing "rhgb quiet" and adding > "systemd.log_level=debug" and check again. > [...] I have removed "rhgb quiet" but not yet added "systemd.log_level=debug". I have also removed my SYSTEMCTL_SKIP_REDIRECT=1 In /vat/log/boot.log I find: Starting SYSV: controls myDaemon daemons... Starting myDaemon: ^[[60G[^[[0;32m OK ^[[0;39m]^M Started SYSV: controls myDaemon daemons. Debig informs me that myDaemon is starting, but rapidly crashing. I am now working on that (after meetings). I assume that once I get that fixed, I can expect #systemctl status myDaemon.service to show something else. Right? Thanks for guidance. Mike. -- Michael D. Berger m.d.berger@xxxxxxxx http://www.rosemike.net/ -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
