Hi Arnaud, > You should not worry too much about this : the installer should do it all for > you ! Well, not really. The installer just adds the dsmserv.rc script to the /etc/rc.d/init.d/ directory. It doesn't create a systemd.service file. Thanks for your reply!
Kind regards, Eric van Loon Air France/KLM Storage & Backup -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of PAC Brion Arnaud Sent: dinsdag 19 november 2019 15:52 To: ADSM-L@VM.MARIST.EDU Subject: Re: systemd.service file example You should not worry too much about this : the installer should do it all for you ! This is what has been created in our shop (ch1inst being the name of our server instance) : [Unit] Documentation=man:systemd-sysv-generator(8) SourcePath=/etc/rc.d/init.d/ch1inst Description=SYSV: Starts/Stops an IBM Tivoli Storage Manager Server instance Before=runlevel3.target Before=runlevel4.target Before=runlevel5.target Before=shutdown.target Before=besclient.service Before=rhnsd.service After=network-online.target After=network.service Conflicts=shutdown.target [Service] Type=forking Restart=no TimeoutSec=5min IgnoreSIGPIPE=no KillMode=process GuessMainPID=no Having this existing as well : /run/systemd/generator.late/ch1inst.service /run/systemd/generator.late/runlevel5.target.wants/ch1inst.service /run/systemd/generator.late/runlevel4.target.wants/ch1inst.service /run/systemd/generator.late/runlevel3.target.wants/ch1inst.service /sys/fs/cgroup/systemd/system.slice/ch1inst.service Cheers ! Arnaud ******************************************************************************************************************************** Backup and Recovery Systems Administrator Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: arnaud.br...@panalpina.com This electronic message transmission contains information from Panalpina and is confidential or privileged. This information is intended only for the person (s) named above. If you are not the intended recipient, any disclosure, copying, distribution or use or any other action based on the contents of this information is strictly prohibited. If you receive this electronic transmission in error, please notify the sender by e-mail, telephone or fax at the numbers listed above. Thank you. ******************************************************************************************************************************** www.panalpina.com -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Schneider, Jim Sent: Tuesday, November 19, 2019 3:39 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: systemd.service file example I don't have an SP service but I've created a service for BMC control-M Agents. It should be easy to make substitutions. Note: This is for Red Hat 7. It won't work on RHEL 6. create file /etc/systemd/system/ctmag.service =========================================================== [Unit] Description=Control-M Agent [Service] Type=forking RemainAfterExit=yes ExecStart=/home/ctmagent/ctm/scripts/rc.agent_user start ExecStop=/home/ctmagent/ctm/scripts/rc.agent_user stop [Install] WantedBy=multi-user.target =========================================================== Issue these commands to activate: systemctl daemon-reload systemctl enable ctmag.service Jim Schneider Essendant -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Michaud, Luc [Analyste principal - environnement AIX] Sent: Tuesday, November 19, 2019 6:53 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] systemd.service file example > However, I would rather use a systemd.service file to start (and stop) SP > during startup and shutdown. Same here !!! Keep me informed if anything comes your way outside this list. We'll be migrating our Blueprint SP (8.1.6.1) servers from AIX to RHEL7 (latest) within the next few months. Regards, Luc ********************************************************************** Information contained in this e-mail message and in any attachments thereto is confidential. If you are not the intended recipient, please destroy this message, delete any copies held on your systems, notify the sender immediately, and refrain from using or disclosing all or any part of its content to any other person. ******************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ********************************************************
