Sponsored Content
Full Discussion: Small automation
Top Forums Shell Programming and Scripting Small automation Post 302836479 by rbatte1 on Wednesday 24th of July 2013 09:17:04 AM
Old 07-24-2013
I don't think I would call it something so confusing. Smilie Perhaps put it in /usr/local/bin to segregate it from anything supplied. I can't actually see the value of flipping it on/off when you would want to know the current state to decide what to do next anyway. SmilieSmilie

If you need to stop/start, then you would have to run your script twice hoping that it is already running. You could just issue:-
Code:
service vsftpd restart

This will always leave it running (unless there is a start-up error)



I hope that this helps. Smilie


Robin
Liverpool/Blackburn
UK
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Help in automation...

Hi All, I need to run the same command on many servers. I am using ssh for the same. Following is the script that I am using to fire the same command on multiple machines. #!/bin/bash # Linux/UNIX box with ssh key based login #SERVERS="iqmevrick,iqmango" # SSH User name USR="root" #... (1 Reply)
Discussion started by: nua7
1 Replies

2. Shell Programming and Scripting

UNIX automation

Hello People, I have an outstanding issue with me I have 5 files at location /usr/abc called 1.DE 1.TXT 2.DE 2.TXT 3.DE 3.TXT 4.DE 4.TXT 5.Fe.ok My work involves few manual process like transfer 1.DE 1.TXT and 5.Fe.ok to /usr/dob location and run one script(for example -... (42 Replies)
Discussion started by: j_panky
42 Replies

3. Shell Programming and Scripting

Scripting for automation

Hi, I would like to know about a automated script which would collect data on a regular day to day basis at a particular time and stores it in a defined path for business analysis. Any help on this is highly appreciable!! Thanks Sara (6 Replies)
Discussion started by: sara23
6 Replies

4. UNIX for Advanced & Expert Users

Need help in automation

Hi, I wanted to automate the scp command where i do not want to enter the password each time. So thought of using expect command. Script is executing without any issues but files are not copied to remote server. Can any one help me? Below is my shell script.. #!/bin/ksh ... (6 Replies)
Discussion started by: balasubramani04
6 Replies

5. Shell Programming and Scripting

automation using python

Im trying to write an automation script using python. I expect this script to log in to a remote server, execute commands and get its output. import pexpect child=pexpect.spawn('ssh myuser@192.168.151.80') child.expect('Password:') child.sendline('mypassword') get_output =... (4 Replies)
Discussion started by: Arun_Linux
4 Replies

6. UNIX for Dummies Questions & Answers

CUPs automation

A little background information: We are a company that uses Sharp MFP devices for everyone to print on. We have a lot of MAC BYOD devices. All printing is done through a product called PaperCut which is ran on a Windows 2008 R2 server. Sharp charges our company for each print job done in... (1 Reply)
Discussion started by: jdmorecraft
1 Replies

7. Shell Programming and Scripting

CVS Automation

Hi All, I am just looking for CVS automation for SQL scripts. Normally Devs will check in new sql scripts or they will update the existing sql scripts with new query. We will take the scripts from CVS and run in DB. I am thinking to automate that process like whenever a new script is checked in... (1 Reply)
Discussion started by: pvmanikandan
1 Replies

8. Shell Programming and Scripting

scp Automation

Hi, I have a requirement to automate SCP command. I have to write the scp command in server1 to copy file from server2 and paste it in server3. I will be passing server2 and server3 as variables. Pls suggest. (1 Reply)
Discussion started by: usrrenny
1 Replies

9. Shell Programming and Scripting

Automation script

Hello All , I came across a tricky solution to devolop . Here is a part of the requirement automation . I have different set of server say : Web ( has 4 servers under it ) , App ( has 4 servers under it ) , DB ( has 2 servers under it ) Above each i have different load balancers , Say : Web... (4 Replies)
Discussion started by: radha254
4 Replies

10. Post Here to Contact Site Administrators and Moderators

UNIX automation

I am using netteza server and i have a list of table names. I need to fetch all the data from these tables and need to create seperate zip files and store in a folder in the server. How can we automate this process. (1 Reply)
Discussion started by: nikhilthms97
1 Replies
DH_INSTALLSYSTEMD(1)                                                 Debhelper                                                DH_INSTALLSYSTEMD(1)

NAME
dh_installsystemd - install systemd unit files SYNOPSIS
dh_installsystemd [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [--no-enable] [--name=name] [unitfile...] DESCRIPTION
dh_installsystemd is a debhelper program that is responsible for enabling, disabling, starting, stopping and restarting systemd unit files. In the simple case, it finds all unit files installed by a package (e.g. bacula-fd.service) and enables them. It is not necessary that the machine actually runs systemd during package installation time, enabling happens on all machines in order to be able to switch from sysvinit to systemd and back. For only generating blocks for specific service files, you need to pass them as arguments, e.g. dh_installsystemd quota.service and dh_installsystemd --name=quotarpc quotarpc.service. FILES
debian/package.service, debian/package@.service If this exists, it is installed into lib/systemd/system/package.service (or lib/systemd/system/package@.service) in the package build directory. debian/package.tmpfile If this exists, it is installed into usr/lib/tmpfiles.d/package.conf in the package build directory. (The tmpfiles.d mechanism is currently only used by systemd.) debian/package.target, debian/package@.target If this exists, it is installed into lib/systemd/system/package.target (or lib/systemd/system/package@.target) in the package build directory. debian/package.socket, debian/package@.socket If this exists, it is installed into lib/systemd/system/package.socket (or lib/systemd/system/package@.socket) in the package build directory. debian/package.mount If this exists, it is installed into lib/systemd/system/package.mount in the package build directory. debian/package.path, debian/package@.path If this exists, it is installed into lib/systemd/system/package.path (or lib/systemd/system/package@.path) in the package build directory. debian/package.timer, debian/package@.timer If this exists, it is installed into lib/systemd/system/package.timer (or lib/systemd/system/package@.timer) in the package build directory. OPTIONS
--no-enable Disable the service(s) on purge, but do not enable them on install. Note that this option does not affect whether the services are started. Please remember to also use --no-start if the service should not be started. --name=name Install the service file as name.service instead of the default filename, which is the package.service. When this parameter is used, dh_installsystemd looks for and installs files named debian/package.name.service instead of the usual debian/package.service. Moreover, maintainer scripts are only generated for units that match the given name. --restart-after-upgrade Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10. In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst. This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon will not get confused by the package being upgraded while it's running before using this option. --no-restart-after-upgrade Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to be stopped in the prerm script and started again in the postinst script. -r, --no-stop-on-upgrade, --no-restart-on-upgrade Do not stop service on upgrade. --no-start Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a corresponding init script). Note that this option does not affect whether the services are enabled. Please remember to also use --no-enable if the services should not be enabled. NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments). Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts. SEE ALSO
debhelper(7) AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org 11.1.6ubuntu2 2018-05-10 DH_INSTALLSYSTEMD(1)
All times are GMT -4. The time now is 10:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy