Visit Our UNIX and Linux User Community


Enabling X11Forwarding Remotely


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting Enabling X11Forwarding Remotely
# 1  
Old 11-11-2009
Enabling X11Forwarding Remotely

When my developer installs a new build, all the servers have X11Forwarding turned off. I would like to write a script to execute from the main server in the suite and have it enable X11Forwarding on all the remote servers.

I created a script that I can execute as root to change the config file and restart the deamon. (The script is convieniently located in a directory that all the servers can mount to.) But... I need to log into 20 machines and su to root to execute it.

Is there a way I can ssh into each machine as root and execute the script?

I've tried something like...

foreach host ($hostlist)
ssh $host su - root -c /here/there/enable_X11script.sh
end


... and it complains about needing to execute in a standard tty.



Any help that would reduce the manual entry across 20 servers would be appreciated.


Scott E.

Previous Thread | Next Thread
Test Your Knowledge in Computers #983
Difficulty: Medium
The first official NetBSD release, NetBSD 0.1, was made on 9 April 1991.
True or False?

9 More Discussions You Might Find Interesting

1. Red Hat

Enabling services.

Hi, I would like to know wheather it is possible to enable same services on another Linux Box, which are enabled on First Linux Server. Example. Server A having some services enabled, I want same kind of services enabled on Server B using single command / using chkconfig command, instead... (4 Replies)
Discussion started by: manoj.solaris
4 Replies

2. Red Hat

XWindow is not enabling !!!

Dear Experts, Our system admin is struggling over a month with an issue regarding xwindow. RHEL 5.4 is our server OS. whenever I export Display with my machine IP and run xclock. It is not working. We are using DHCP. Please tell me what checks and actions should be taken from our sys admin point... (8 Replies)
Discussion started by: saifurshaon
8 Replies

3. UNIX for Dummies Questions & Answers

Help with enabling ports.

Hi All, How to enable or disable a port in solaris 10. Thanks in advance.:) (3 Replies)
Discussion started by: rama krishna
3 Replies

4. Solaris

Enabling MQ Listeners

Hi I've been trying to change the services for MQ listeners using inetaconv and inetadm. The MQ was already installed and Im trying to change the QManager name. Ive creted the appropriate files (MQSeries-tcp.xml) and am now trying to enable MQSeries and then refresh the service: inetadm... (2 Replies)
Discussion started by: billy_mega
2 Replies

5. Cybersecurity

Enabling C2 audit

hey guys, im going to enable C2 auditing on a sun box, i know how to do it, but im just wondering if there are any issues or problems that i may run into. this will be my first major change (since i have to reset the box) since i joined this company and i dont really wanna kill their servers, so... (2 Replies)
Discussion started by: roguekitton
2 Replies

6. AIX

Enabling 64 bit

Hi, I am having some issues installing Oracle 10G Release 2 on my AIX 5.2L box. Here is what i do: 1- Extract the 10gr2 64bit cpio file using cpio -icdmv < install_file.cpio 2- Once the file is extracted, i run the rootpre.sh file. I got no error message so far everything is fine 3-... (3 Replies)
Discussion started by: Netghost
3 Replies

7. Solaris

Enabling NTP ....

Hi , What is the best way to configure NTP ( Network Timing Protocol ).. on Solaris 9 .... I have 5 Servers. Regards (2 Replies)
Discussion started by: ArabOracle.com
2 Replies

8. UNIX for Dummies Questions & Answers

enabling TFTP

ive been trying to enable a tftp service on a unix box using the command atftpd --daemon but when i scan the open ports using nmap it doesnt show that port 21 as up does anyone know the reason... ive tried /etc/init.d/atftpd start , it didnt work if i type atftpd by it self it gives me a set... (2 Replies)
Discussion started by: ratamahatta
2 Replies

9. Programming

Enabling Far in GCC

hello, i want to enable far in gcc, how to enable this. pls reply back thanx in advance. svh (1 Reply)
Discussion started by: svh
1 Replies
DH_INSTALLINIT(1)						     Debhelper							 DH_INSTALLINIT(1)

NAME
dh_installinit - install service init files into package build directories SYNOPSIS
dh_installinit [debhelperoptions] [--name=name] [-n] [-R] [-r] [-d] [--params] DESCRIPTION
dh_installinit is a debhelper program that is responsible for installing init scripts with associated defaults files. In compatibility levels up to 11, dh_installinit also handled upstart job files and systemd service files. It also automatically generates the postinst and postrm and prerm commands needed to set up the symlinks in /etc/rc*.d/ to start and stop the init scripts. In compat 10 or earlier: If a package only ships a systemd service file and no sysvinit script is provided, you may want to exclude the call to dh_installinit for that package (e.g. via -N). Otherwise, you may get warnings from lintian about init.d scripts not being included in the package. FILES
debian/package.init If this exists, it is installed into etc/init.d/package in the package build directory. debian/package.default If this exists, it is installed into etc/default/package in the package build directory. debian/package.upstart In compatibility level 11, this file will trigger an error with a reminder about ensuring the proper removal of the upstart file in the previous package version. Please consider using the "rm_conffile" feature from dh_installdeb(1) to ensure the proper removal of previous upstart files. In compatibility level 10, if this file exists, it is installed into etc/init/package.conf in the package build directory. debian/package.service If this exists, it is installed into lib/systemd/system/package.service in the package build directory. Only used in compat levels 10 and below. 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.) Only used in compat levels 10 and below. OPTIONS
-n, --no-scripts Do not modify postinst/postrm/prerm scripts. -o, --only-scripts Only modify postinst/postrm/prerm scripts, do not actually install any init script, default files, upstart job or systemd service file. May be useful if the file is shipped and/or installed by upstream in a way that doesn't make it easy to let dh_installinit find it. Caveat: This will bypass all the regular checks and unconditionally modify the scripts. You will almost certainly want to use this with -p to limit, which packages are affected by the call. Example: override_dh_installinit: dh_installinit -pfoo --only-scripts dh_installinit --remaining -R, --restart-after-upgrade Do not stop the init script until after the package upgrade has been completed. This is the default behaviour in compat 10. In early compat levels, the default was to stop the script in the prerm, and starts 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 init script on upgrade. This has the side-effect of not restarting the service as a part of the upgrade. If you want to restart the service with minimal downtime, please use --restart-after-upgrade (default in compat 10 or later). If you want the service to be restarted but be stopped during the upgrade, then please use --no-restart-after-upgrade (note the "after- upgrade"). Note that the --no-restart-on-upgrade alias is deprecated and will be removed in compat 12. This is to avoid confusion with the --no-restart-after-upgrade option. The --no-stop-on-upgrade variant was introduced in debhelper 10.2 (included in Debian stretch). --no-start Do not start the init script on install or upgrade, or stop it on removal. Only call update-rc.d. Useful for rcS scripts. --no-enable Disable the init script on purge, but do not enable them on install. This implies a versioned dependency on init-system-helpers (= 1.51)> as it is the first (functional) version that supports <update-rc.d <script defaults-disabled>>. 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. Cannot be combined with -uparams, --update-rcd-params=params, or -- params. -d, --remove-d Remove trailing d from the name of the package, and use the result for the filename the upstart job file is installed as in etc/init/ , and for the filename the init script is installed as in etc/init.d and the default file is installed as in etc/default/. This may be useful for daemons with names ending in d. (Note: this takes precedence over the --init-script parameter described below.) -uparams --update-rcd-params=params -- params Pass params to update-rc.d(8). If not specified, defaults (or defaults-disabled with --no-enable) will be passed to update-rc.d(8). Cannot be combined with --no-enable. --name=name Install the init script (and default file) as well as upstart job file using the filename name instead of the default filename, which is the package name. When this parameter is used, dh_installinit looks for and installs files named debian/package.name.init, debian/package.name.default and debian/package.name.upstart instead of the usual debian/package.init, debian/package.default and debian/package.upstart. --init-script=scriptname Use scriptname as the filename the init script is installed as in etc/init.d/ (and also use it as the filename for the defaults file, if it is installed). If you use this parameter, dh_installinit will look to see if a file in the debian/ directory exists that looks like package.scriptname and if so will install it as the init script in preference to the files it normally installs. This parameter is deprecated, use the --name parameter instead. This parameter is incompatible with the use of upstart jobs. --error-handler=function Call the named shell function if running the init script fails. The function should be provided in the prerm and postinst scripts, before the #DEBHELPER# token. NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command. Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts. SEE ALSO
debhelper(7) This program is a part of debhelper. AUTHORS
Joey Hess <joeyh@debian.org> Steve Langasek <steve.langasek@canonical.com> Michael Stapelberg <stapelberg@debian.org> 11.1.6ubuntu2 2018-05-10 DH_INSTALLINIT(1)

Featured Tech Videos