Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Connecting to UNIX through telnet Post 302934293 by cero on Friday 6th of February 2015 02:33:58 AM
Old 02-06-2015
Start telnetd if it is already installed on that system. Because the telnet protocol is deemed insecure that service may not be installed by default, so you may have to install it.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

connecting to windows from unix

how to connect to windows from unix??? (7 Replies)
Discussion started by: hemant30
7 Replies

2. UNIX for Advanced & Expert Users

Connecting to a database via UNIX

hello - Is it possible to connect to a database at the command line to an Oracle instance whilst logged in on the unix box i.e. not using a script Cheers (Running Solaris) Also if anyone has any info on how a Citirix ICA client might be helpful here that would be appreciated Cheers (1 Reply)
Discussion started by: penfold
1 Replies

3. Shell Programming and Scripting

connecting unix to vb

how can i check to number of files and directory containing no data in whole system and display it if 'home' is to root directory it contains 10 subdirectory and many files (1 Reply)
Discussion started by: shafique
1 Replies

4. Shell Programming and Scripting

connecting to another unix box

Hi gurus, I am entirely new to unix. So if my questions are foolish, please bear with me. I have two unix boxes A and B. Is it possible to execute a command or a shell script in box B standing in box A. I mean if i log in to box A and execute a shell script, it should be able to login... (7 Replies)
Discussion started by: bade_miya
7 Replies

5. UNIX for Dummies Questions & Answers

Connecting as CONSOLE using Telnet.

Hi, I need to connect as CONSOLE from my WinXP PC to a Solaris server (Solaris 9 SPARC) using telnet. I cannot use HyperTerminal as there is no direct link between my PC and the server (it is a remote server). How to do this? Regards. M. (3 Replies)
Discussion started by: mahatma
3 Replies

6. Shell Programming and Scripting

Connecting To Different Unix Box

Hi gurus I want to to connect to a different unix box from current unix box and navigate to a folder and check if the log files are generated for every 10 minutes in the another unix box. how do i go about this requirement. is there a way to connect to different unix boxes. thanks raghavendra (5 Replies)
Discussion started by: ragha81
5 Replies

7. UNIX for Dummies Questions & Answers

Connecting to UNIX server

Hi, My knowledge bucket of UNIX is almost empty. I have developed an application in EXCEL which can create XML files (Metadata) from Binaries. These binaries are stored in UNIX server on regular intervals. Currently I am transferring all binaries(GBs of files) to WINDOWS using WINSCP and... (2 Replies)
Discussion started by: bobs
2 Replies

8. SuSE

Error when connecting to telnet

Hi , I am using SuSE 10. When I connect to telnet after entering password I get an error message "Module unknown". Kindly let me know the solution if any of you have faced similar issues before. (1 Reply)
Discussion started by: Laksmi
1 Replies

9. Shell Programming and Scripting

Help need Connecting to Oracle DB from Unix

I have a table called CLARIFICATION in one of my schema in Oracle Data Base. I have to connect to oracle Data Base from Unix and compare the one of the column(Exec_Date) in CLARIFICATION table with Sysdate.If Exec_Date = Sysdate go head and run rest of the script otherwise exit out with out... (2 Replies)
Discussion started by: veeru
2 Replies

10. Shell Programming and Scripting

Connecting to SVN from UNIX

Hi, I'm new to Unix,I want to connect to Sub Version(SVN) through Unix. Please let know what command i need to use. Thanks, Madhuri (3 Replies)
Discussion started by: srimadhuri
3 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 06:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy