Differences

This shows you the differences between two versions of the page.

--- en:utility-scripts:chttl [2025/01/06 05:34] – [Code download] Webmaster VitaNetworks
+++ en:utility-scripts:chttl [2025/01/06 07:46] (current) – Webmaster VitaNetworks
@@ Line 2: / Line 2: @@
 ''chttl'' — Temporarily override the system's default TTL.
-<WRAP center round tip 80%>
-===== Make it a function =====
-This was originally written as a bash function. It was changed early on to ''sh'' for POSIX compliance but it was wrapped in a single thing to make it easy to change it back. Simply remove the first and last lines and add the remaining code to your bash functions file(s).
-</WRAP>
 ===== What does it do? =====
@@ Line 12: / Line 7: @@
 ===== Wouldn't an alias be shorter to do? =====
-Yes, but the command changes across operative systems.
+Yes, but the command changes across operative systems. You'd need an alias for each, which is a bit more complicated to sync unless you add some logic to your aliases file, but wouldn't that be just about the same? bash config files, //whatever//.
 ===== Is there something else? =====
-- This is the first [intentionaly] POSIX-compliant script we've ever written.
+- This is the first [intentionaly] POSIX-compliant script we've ever written.\\
-- It works on macOS, Linux and FreeBSD.
+- It works on macOS, Linux and FreeBSD.\\
-- It can be used to set the value back to where it was as well, simply add it at the end.
+- It can be used to set the value back to where it was as well, simply add it at the end.\\
-- It's not a permanent modification.
+- It's not a permanent modification.\\
-  Depending on the OS, you might need to create a file in a specific location or issue a special command that sets preference files.
+  - Depending on the OS, you might need to create a file in a specific location or issue a special command that sets preference files.
+==== Make it a function ====
+This was originally written as a bash function. It was changed early on to ''sh'' for portability reasons but nevertheless it was wrapped in a single unit to make it easy to change it back. All you need is to remove the shebang (first) line and the call out or invocation (last) line from the script. Then paste the remainder of the code in your bash functions file(s).
+=== Using a functions file ===
+As a login shell, bash process config files in the following order:
+- ''/etc/profile''
+- ''~/.bash_profile''
+- ''~/.bash_login'', and
+- ''~/.profile'',
+Typically ''~/.bash_profile'' would call ''~/.bashrc'' which will be executed every single new CLI session. i.e;\\
+''if [ -f ~/.bashrc ]; then . ~/.bashrc; fi''\\
+(meaning "//if ''~/.bashrc'' exists, run it// ".)
+You may follow the bash's own example by invoking the functions file from ''~/.bash_profile'' e.g; ''if [ -f "${HOME}/bin/bashfunctions" ]; then . "${HOME}/bin/bashfunctions"; fi'' where the file was created to live alongside your scritps on ''"${HOME}/bin"'' and it would be a much easier job syncing things across systems.
+<code>
+[Sun05@23:20:52][vuser@vpro:~] $〉ls
+total n
+-rw-------    1 vuser  vgroup    12K Jan  5 23:04 .bash_history
+-rw-r-xr-x@   1 vuser  vgroup   1.7K Oct 25 16:51 .bash_profile*
+########################################################################################################
+#↑↑↑ Add 'if [ -f "${HOME}/bin/bashfunctions" ]; then . "${HOME}/bin/bashfunctions"; fi'            ↑↑↑#
+########################################################################################################
+-rw-r--r--    1 vuser  vgroup   1.5K Jul  3  2024 .bash_profile.bak
+-rw-r-xr-x@   1 vuser  vgroup   1.1K Mar 27  2024 .bash_profile.pysave*
+drwx------   16 vuser  vgroup   512B Oct  7 16:09 .bash_sessions/
+-rw-r-xr-x@   1 vuser  vgroup   4.7K Oct 14 16:01 .bashrc*
+drwxr-xr-x  172 vuser  vgroup   5.4K Jan  5 16:18 bin/
+[Sun05@23:50:41][vuser@vpro:~] $〉ls bin
+total n
+drwxr-xr-x  12 vuser  vgroup   384B Mar 20  2024 .git/
+-rwxr-xr-x   1 vuser  vgroup    86B May  1  2022 .zshrc*
+drwxr-xr-x  17 vuser  vgroup   544B Sep 22  2020 argbash/
+drwxr-xr-x   2 vuser  vgroup    64B Feb  9  2023 assets/
+-rwxr-xr-x   1 vuser  vgroup   102B May  1  2022 backupbashp*
+-rwxr-xr-x   1 vuser  vgroup   2.6K Oct 18 13:02 bashaliases*
+-rwxr-xr-x@  1 vuser  vgroup   6.8K Jan  5 00:10 bashfunctions*
+########################################################################################################
+#↑↑↑         Functions file example                                                                 ↑↑↑#
+########################################################################################################
+-rwxr-xr-x   1 vuser  vgroup   3.5K Nov  1 17:20 bashvars*
+-rwxr-xr-x   1 vuser  vgroup    30B May  1  2022 catprivkey*
+-rwxr-xr-x   1 vuser  vgroup    34B May  1  2022 catpubkey*
+-rwxr-xr-x   1 vuser  vgroup    20K Feb 25  2023 ciscokvm*
+-rwxr-xr-x   1 vuser  vgroup   119B Oct  3 02:04 codehere*
+-rwxr-xr-x   1 vuser  vgroup   235B May  1  2022 fixsmb*
+-rwxr-xr-x   1 vuser  vgroup    55B May  1  2022 fixsshperms*
+-rwxr-xr-x@  1 vuser  vgroup   1.0K Jul 11 07:30 flushdns*
+-rwxr-xr-x   1 vuser  vgroup   128B May 28  2022 getcerts*
+-rwxr-xr-x   1 vuser  vgroup   262B May 28  2022 getmstr*
+-rwxr-xr-x   1 vuser  vgroup    51B May  1  2022 hapchk*
+-rwxr-xr-x   1 vuser  vgroup   243B May  1  2022 hapcmd*
+-rwxr-xr-x   1 vuser  vgroup    52B May  1  2022 hapinfo*
+-rwxr-xr-x   1 vuser  vgroup    40B May  1  2022 hapjrnl*
+-rwxr-xr-x   1 vuser  vgroup    30K Oct 23  2022 hapreset*
+-rwxr-xr-x   1 vuser  vgroup    51B May  1  2022 hapstart*
+-rwxr-xr-x   1 vuser  vgroup    50B May  1  2022 hapstop*
+-rwxr-xr-x@  1 vuser  vgroup   2.6K Nov 11 17:49 heupdate*
+-rwxr-xr-x   1 vuser  vgroup   1.8K Oct 31 17:59 lopkg*
+-rwxr-xr-x   1 vuser  vgroup   1.9K Oct 23  2022 lports*
+-rwxr-xr-x   1 vuser  vgroup   272B May  1  2022 lsvch*
+-rwxr-xr-x   1 vuser  vgroup    17K Apr 22  2024 pppkg*
+-rwxr-xr-x   1 vuser  vgroup    21K Jan  1  2023 ppull*
+-rwxr-xr-x@  1 vuser  vgroup    15K Apr  9  2024 ppush*
+-rwxr-xr-x   1 vuser  vgroup    11K Nov  3  2022 printMESSAGE*
+-rwxr-xr-x   1 vuser  vgroup    80B May  1  2022 rmkh*
+-rwxr-xr-x   1 vuser  vgroup   5.6K Jan 21  2023 rmkhk*
+-rwxr-xr-x   1 vuser  vgroup    41B Dec  7  2022 vimhosts*
+-rwxr-xr-x   1 vuser  vgroup    30B May  1  2022 vimsshconfig*
+-rwxr-xr-x@  1 vuser  vgroup    19K Nov 18 09:42 vncadeploy*
+-rwxr-xr-x   1 vuser  vgroup    84K Jan 23  2023 vprep*
+-rwxr-xr-x   1 vuser  vgroup   3.8K Oct 20  2023 vsphere2unraid*
+-rwxr-xr-x   1 vuser  vgroup   505B Jan 22  2024 xdex*
+-rwxr-xr-x   1 vuser  vgroup   403B Dec 17  2022 zfsarctune*
+</code>
 ===== Syntax =====
 The script takes one or no arguments; any additional argument(s) after the first one should be ignored.
@@ Line 84: / Line 154: @@
 On Linux systems, you can drop it in the ''bin'' subdirectory of your home folder (''~/bin'' or ''$HOME/bin'') to make it available anywhere on the CLI. Don't forget to make it executable first (e.g; ''chmod +x $HOME/bin/chttl'').
+===== A note about privileges =====
+This a task that requires superadmin privileges. The script does not attempt to elevate your permissions at any time; you will need to do that yourself by prepending ''sudo'', being logged in as ''root'', or however you wish. That is your call.
+===== Anti-corporate takeover measure (licensing) =====
+chttl — Temporarily override the system's default TTL.\\
+Copyright (C) 2025  Gustavo Domínguez
+This program is free software: you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+GNU General Public License for more details.
+You should have received a copy of the GNU General Public License
+along with this program.  If not, see https://www.gnu.org/licenses/