[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[AWIPS #LOF-511733]: launch "sudo edex start" on system boot



Hi Pete,

systemctl is a very common management service command on linux and I'm guessing 
a number of your other services use it as well (and is very well documented 
online by users). Another one is chckconfig (they both essentially do the same 
thing). In our edex start up script, the first time EDEX is ran, it actually 
already sets edex_postgres, httpdp-pypies, qpidd, and edex_camel to start on 
boot already. Are you sure they don't already start on boot? Here's our default 
configuration:

[awips@edex1 ~]$  chkconfig --list

Note: This output shows SysV services only and does not include native
      systemd services. SysV configuration data might be overridden by native
      systemd configuration.

      If you want to list systemd services use 'systemctl list-unit-files'.
      To see services enabled on particular target use
      'systemctl list-dependencies [target]'.

edex_camel      0:off   1:off   2:on    3:on    4:on    5:on    6:off
edex_postgres   0:off   1:off   2:on    3:on    4:on    5:on    6:off
httpd-pypies    0:off   1:off   2:on    3:on    4:on    5:on    6:off
qpidd           0:off   1:off   2:on    3:on    4:on    5:on    6:off


Again both these commands are very common and can be read up the differences: 
https://bencane.com/2012/01/19/cheat-sheet-systemctl-vs-chkconfig/


> Thank you yet again - clarification -- we run these commands once from a 
> command line as root and that sets them up to be run upon boot -- correct?  
> 

Thanks,

Tiffany Meyer
AWIPS Lead Software Engineer
UCAR-Unidata

If you're interested, please feel free to fill out a survey about the support 
you receive:  
https://docs.google.com/forms/d/e/1FAIpQLSeDIkdk8qUMgq8ZdM4jhP-ubJPUOr-mJMQgxInwoAWoV5QcOw/viewform

Ticket Details
===================
Ticket ID: LOF-511733
Department: Support AWIPS
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.