This file is indexed.

/usr/bin/slonik_uninstall_nodes is in slony1-2-bin 2.2.4-3.

This file is owned by root:root, with mode 0o755.

The actual contents of the file can be viewed below.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
#!/usr/bin/perl
# 
# Author: Christopher Browne
# Copyright 2004-2009 Afilias Canada

use Getopt::Long;

# Defaults
$CONFIG_FILE = '/etc/slony1/slon_tools.conf';
$SHOW_USAGE  = 0;

# Read command-line options
GetOptions("config=s" => \$CONFIG_FILE,
	   "help"     => \$SHOW_USAGE);

my $USAGE =
"Usage: uninstall_nodes [--config file]

    Removes Slony configuration from all nodes in a cluster.

Restores all tables to the unlocked state, with all original user       
triggers, constraints and rules, eventually added Slony-I specific      
serial key columns dropped and the Slony-I schema dropped. The node     
becomes a standalone database. The data is left untouched.              
 
The difference between UNINSTALL NODE and DROP NODE is that all         
UNINSTALL NODE does is to remove the Slony-I configuration; it doesn't  
drop the node's configuration from replication.                         

";

if ($SHOW_USAGE) {
  print $USAGE;
  exit 0;
}

require '/usr/share/slony1/slon-tools.pm';
require $CONFIG_FILE;

my $slonik = '';
$slonik .= genheader();
foreach my $node (@NODES) {
    next if $node == $MASTERNODE; # Do this one last
    $slonik .= "  uninstall node (id=$node);\n";
}
$slonik .= "  uninstall node (id=$MASTERNODE);\n";

run_slonik_script($slonik, 'UNINSTALL NODE');