02-17-2015
Should be the values in /etc/sysctl.conf
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I am working with Solaris 9 Sun Blade-100.I am doing some changes for serial port and by mistaken I changed the serial port /dev/term/a variables.
So I need to make the changes fro /dev/term/a same as /dev/term/b.
So please tell me how can I do that ?? (1 Reply)
Discussion started by: smartgupta
1 Replies
2. AIX
May I know what is the TCP/UCP port range for any default AIX NFS? Based on rpcinfo -p, I got the following output:
program vers proto port service
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100000 4 ... (4 Replies)
Discussion started by: famasutika
4 Replies
3. Shell Programming and Scripting
Hi;
For sure there's an easy answer to this one that I am not finding..
I first set a variable, say
b1a:] max=5
then I want to use max to set the range for a for loop like so (it should run for i in 1:5)
b1a:] for i in {1..$max}; do echo $i; done
{1..5}
I would like the output... (2 Replies)
Discussion started by: jbr950
2 Replies
4. AIX
Hi Guys,
Please could you tell me if it is possible to have a single rule/filter to allow a certain port range instead of a separate rule for each port?
I'm sure it must be possible but I am unable to find the syntax.
Thanks
Chris (4 Replies)
Discussion started by: chrisstevens
4 Replies
5. Shell Programming and Scripting
I have files being generated in format A20140326.00........ to A20140326.24.............
I need to copy these hourly basis from one location to another.
Eg. If i copy from 14 to 19 the hour, I use wildcard as A201403226.1*.
Requirement is : I need to copy from 06 hour and wil run the script... (1 Reply)
Discussion started by: Saidul
1 Replies
6. UNIX for Dummies Questions & Answers
I want to limit all *outbound* traffic on eth0 (or all *.*) on port 25 to a specific (allowed) range...
I.E.
192.168.1.5 (local ip) tries to connect to 1.2.3.4:25 (outside real world ip)
It can proceed because 1.2.3.0/24 is the allowed range
Now, 192.168.1.5 (local ip) tries to connect to... (1 Reply)
Discussion started by: holyearth
1 Replies
7. Shell Programming and Scripting
Input File:
2000 3
1998 2
1997 2
1994 1
1991 1
1989 1
1987 2
1986 2
1985 1
1984 1
.
.
10 277256
9 278274
8 282507
7 284837
6 287066
5 292967 (4 Replies)
Discussion started by: perl_beginner
4 Replies
8. AIX
I'll start with I'm not an AIX expert, I inherited a lot of AIX servers to maintain.
My problem is on AIX 7.1 TL4 SP4 environments. I'm running named as a DNS forwarder only to internal DNS servers.
These AIX servers have a customized UDP ephemeral port range to avoid conflicting with the... (0 Replies)
Discussion started by: seanc
0 Replies
9. UNIX for Beginners Questions & Answers
hi,
i would like to create a bash script that check which port in my Linux server are closed (not in use) from a specific range, port range (3000-3010).
the print output need to be only 1 port, and it will be nice if the output will be saved as a variable or in same file.
my code is:
... (2 Replies)
Discussion started by: yossi
2 Replies
10. UNIX for Beginners Questions & Answers
Ca21chr2_C_albicans_SC5314 2159343 2228327 Ca21chr2_C_albicans_SC5314 636587 638608
Ca21chr2_C_albicans_SC5314 5286 50509 Ca21chr2_C_albicans_SC5314 634021 636276
Ca21chr2_C_albicans_SC5314 1886545 1900975 Ca21chr2_C_albicans_SC5314 610758 613544... (9 Replies)
Discussion started by: cryptodice
9 Replies
LEARN ABOUT MOJAVE
systemd-sysctl.service
SYSTEMD-SYSCTL.SERVICE(8) systemd-sysctl.service SYSTEMD-SYSCTL.SERVICE(8)
NAME
systemd-sysctl.service, systemd-sysctl - Configure kernel parameters at boot
SYNOPSIS
/lib/systemd/systemd-sysctl [OPTIONS...] [CONFIGFILE...]
systemd-sysctl.service
DESCRIPTION
systemd-sysctl.service is an early boot service that configures sysctl(8) kernel parameters by invoking /lib/systemd/systemd-sysctl.
When invoked with no arguments, /lib/systemd/systemd-sysctl applies all directives from configuration files listed in sysctl.d(5). If one
or more filenames are passed on the command line, only the directives in these files are applied.
In addition, --prefix= option may be used to limit which sysctl settings are applied.
See sysctl.d(5) for information about the configuration of sysctl settings. After sysctl configuration is changed on disk, it must be
written to the files in /proc/sys before it takes effect. It is possible to update specific settings, or simply to reload all
configuration, see Examples below.
OPTIONS
--prefix=
Only apply rules with the specified prefix.
-h, --help
Print a short help text and exit.
--version
Print a short version string and exit.
EXAMPLES
Example 1. Reset all sysctl settings
systemctl restart systemd-sysctl
Example 2. View coredump handler configuration
# sysctl kernel.core_pattern
kernel.core_pattern = |/libexec/abrt-hook-ccpp %s %c %p %u %g %t %P %I
Example 3. Update coredump handler configuration
# /lib/systemd/systemd-sysctl --prefix kernel.core_pattern
This searches all the directories listed in sysctl.d(5) for configuration files and writes /proc/sys/kernel/core_pattern.
Example 4. Update coredump handler configuration according to a specific file
# /lib/systemd/systemd-sysctl 50-coredump.conf
This applies all the settings found in 50-coredump.conf. Either /etc/sysctl.d/50-coredump.conf, or /run/sysctl.d/50-coredump.conf, or
/usr/lib/sysctl.d/50-coredump.conf will be used, in the order of preference.
See sysctl(8) for various ways to directly apply sysctl settings.
SEE ALSO
systemd(1), sysctl.d(5), sysctl(8),
systemd 237 SYSTEMD-SYSCTL.SERVICE(8)