Mdthbs

Should I email my professor about a recommendation letter if he has offered me a job?

How do some PhD students get 10+ papers? Is that what I need for landing good faculty position?

Are those flyers about apartment purchase a scam?

Why aren't rainbows blurred-out into nothing after they are produced?

Can the IPA represent all languages' tones?

How is являться different from есть and быть

How to "add" units to results of pgfmathsetmacro?

Graphs for which a calculus student can reasonably compute the arclength

Case Condition for two lines

Swap on SSD in 2019?

Why is the Lucas test not recommended to differentiate higher alcohols?

What is the farthest a camera can see?

How would you translate this? バタコチーズライス

Are there any other rule mechanics that could grant Thieves' Cant?

Is this n-speak?

My cat is a houdini

Running code generated in realtime in JavaScript with eval()

Is it possible to grow new organs through exposure to radioactivity?

Tempoverlustspiel

Are employers legally allowed to pay employees in goods and services equal to or greater than the minimum wage?

How to remove ambiguity: "... lives in the city of H, the capital of the province of NS, WHERE the unemployment rate is ..."?

Is there a SQL/English like language that lets you define formulations given some data?

Why is the result of ('b'+'a'+ + 'a' + 'a').toLowerCase() 'banana'?

A torrent of foreign terms

do changes in /etc/security/limits.conf require a reboot?

How do I start a process with a nice value of -20 and not give it root privilege?Changes to /etc/security/limits.conf and /etc/security/limits.d/20-nproc.conf have no effectHow can I allow a user to prioritize a process to negative niceness?Where is the limit set? bash: fork: retry: No child processesUnable to change ulimit settingSetting ulimits without PAMlimits that are set in an unmodified environmentWhat are the effects of increasing hard and soft limits for ldap userProcess specific ulimit still low after changes to soft and hard ulimitsFile descriptor limits in /etc/system vs /etc/sysctl.conf vs /etc/security/limits.conf on Solarisulimit vs /etc/security/limits.confOpenfiles limit automatically decreases when passing 2^21, Ubuntu 16.04/etc/security/limits.conf not appliedIncreasing open files limit for all processes: Do I need to set Soft/Hard limits?Open file limits not increased for redis user despite change in /etc/security/limits.conf

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

141

31

Do changes in /etc/security/limits.conf require a reboot before taking effect?

Like if I have a script that sets the following limits in /etc/security/limits.conf, does this require to reboot the system before those limits will take effect?

* hard nofile 94000

* soft nofile 94000

* hard nproc 64000

* soft nproc 64000

limit ulimit

share|improve this question

edited 16 hours ago

Julia M.

322 bronze badges

asked Jan 9 '14 at 18:51

Alexej MaguraAlexej Magura

1,72066 gold badges1717 silver badges3636 bronze badges

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  logout should be enough
  
  – UVV
  Jan 9 '14 at 18:59
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Edit the file /etc/security/limits.d/90-nproc.conf and reboot you system
  
  – user80746
  Aug 13 '14 at 17:48
  

  
  
  
  

add a comment | 

141

31

Do changes in /etc/security/limits.conf require a reboot before taking effect?

Like if I have a script that sets the following limits in /etc/security/limits.conf, does this require to reboot the system before those limits will take effect?

* hard nofile 94000

* soft nofile 94000

* hard nproc 64000

* soft nproc 64000

limit ulimit

share|improve this question

edited 16 hours ago

Julia M.

322 bronze badges

asked Jan 9 '14 at 18:51

Alexej MaguraAlexej Magura

1,72066 gold badges1717 silver badges3636 bronze badges

• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  logout should be enough
  
  – UVV
  Jan 9 '14 at 18:59
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Edit the file /etc/security/limits.d/90-nproc.conf and reboot you system
  
  – user80746
  Aug 13 '14 at 17:48
  

  
  
  
  

add a comment | 

Do changes in /etc/security/limits.conf require a reboot before taking effect?

Like if I have a script that sets the following limits in /etc/security/limits.conf, does this require to reboot the system before those limits will take effect?

* hard nofile 94000

* soft nofile 94000

* hard nproc 64000

* soft nproc 64000

limit ulimit

share|improve this question

edited 16 hours ago

Julia M.

322 bronze badges

asked Jan 9 '14 at 18:51

Alexej MaguraAlexej Magura

1,72066 gold badges1717 silver badges3636 bronze badges

* hard nofile 94000

* soft nofile 94000

* hard nproc 64000

* soft nproc 64000

share|improve this question

edited 16 hours ago

Julia M.

322 bronze badges

asked Jan 9 '14 at 18:51

Alexej MaguraAlexej Magura

1,72066 gold badges1717 silver badges3636 bronze badges

share|improve this question

edited 16 hours ago

Julia M.

322 bronze badges

asked Jan 9 '14 at 18:51

Alexej MaguraAlexej Magura

1,72066 gold badges1717 silver badges3636 bronze badges

edited 16 hours ago

Julia M.

322 bronze badges

edited 16 hours ago

Julia M.

322 bronze badges

asked Jan 9 '14 at 18:51

Alexej MaguraAlexej Magura

1,72066 gold badges1717 silver badges3636 bronze badges

asked Jan 9 '14 at 18:51

Alexej MaguraAlexej Magura

1,72066 gold badges1717 silver badges3636 bronze badges

5 Answers
5

active

oldest

votes

105

No but you should close all active sessions windows. They still remember the old values. In other words, log out and back in.
Every remote new session or a local secure shell take effect of the limits changes.

share|improve this answer

edited Jan 2 '15 at 3:08

Gilles

569k136136 gold badges11741174 silver badges16861686 bronze badges

answered Jan 9 '14 at 19:02

SlyxSlyx

2,82722 gold badges1313 silver badges2424 bronze badges

• 
  
  
  

  
  17
  

  
  
  
  
  
  

  
  
  What if I want to set the limits for a user that doesn't have a login, like if I want to set the nofile limit to 94000 for the mongodb user? How'd I do that without a reboot? Would I just need to restart the mongodb service?
  
  – Alexej Magura
  Jan 9 '14 at 19:35
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  @AlexejMagura You can modify the the rlimits of running processes with the prlimit command.
  
  – Bratchley
  Jan 9 '14 at 23:46
  

  
  
  
  


• 
  
  
  

  
  7
  

  
  
  
  
  
  

  
  
  @Gilles, thanks for the precisions, I edited my answer to to avoid ambiguity. However Starting a new service using sudo service mongodb restart is enough to let the service running with the new limit values.
  
  – Slyx
  Jan 10 '14 at 15:01
  

  
  
  
  


• 
  
  
  

  
  6
  

  
  
  
  
  
  

  
  
  if you are using Ubuntu, and mongodb is started by upstart, then changing these limits will not affect mongodb. As upstart does not read /etc/security config bugs.launchpad.net/ubuntu/+source/upstart/+bug/938669 you must set limit stanza in its upstart config file.
  
  – HVNSweeting
  Jan 19 '15 at 3:22
  

  
  
  
  


• 
  
  
  

  
  5
  

  
  
  
  
  
  

  
  
  It's another issue. upstart by design ignores the limits set in /etc/security/limits.conf.
  
  – Slyx
  Jan 20 '15 at 11:00
  

  
  
  
  

add a comment | 

34

Apply the changes directly to a running process if you have prlimit installed (comes with util-linux-2.21)

prlimit --pid <pid> --<limit>=<soft>:<hard>

for example

prlimit --pid 12345 --nofile=1024:2048

Refer here

share|improve this answer

answered Apr 6 '15 at 10:21

RamRam

63122 gold badges1111 silver badges1818 bronze badges

add a comment | 

29

To temporarily set the open files limit for the user you are currently logged in under (e.g. 'root'):You can also use the ulimit command to change the values in your current shell. However, hard limits can only be adjusted downwards unless you're root.

Example:

# ulimit -a

core file size          (blocks, -c) 0

data seg size           (kbytes, -d) unlimited

scheduling priority             (-e) 0

file size               (blocks, -f) unlimited

pending signals                 (-i) 62449

max locked memory       (kbytes, -l) 64

max memory size         (kbytes, -m) unlimited

open files                      (-n) 1024

pipe size            (512 bytes, -p) 8

POSIX message queues     (bytes, -q) 819200

real-time priority              (-r) 0

stack size              (kbytes, -s) 10240

cpu time               (seconds, -t) unlimited

max user processes              (-u) 1024

virtual memory          (kbytes, -v) unlimited

file locks                      (-x) unlimited

To change the nofile to 94000 you can do:

ulimit -n 94000

share|improve this answer

edited May 25 '17 at 10:59

Community♦

1

answered Jan 10 '14 at 8:44

BoogyBoogy

81866 silver badges88 bronze badges

add a comment | 

14

Limits are inherited from a parent process to its child processes. Processes running as root can change limits arbitrarily; other processes cannot increase hard limits. Thus the hard limits set by the login process affect all the processes in a session.

If you change /etc/security/limits.conf, this will affect all new sessions, and processes in these new sessions. It won't affect processes that are already running, nor processes started by processes that are already running.

So if you need to increase some limits, you'll have to either log out and back in, or start another session (e.g. with ssh localhost, or on another console).

share|improve this answer

answered Jan 10 '14 at 2:29

GillesGilles

569k136136 gold badges11741174 silver badges16861686 bronze badges

add a comment | 

4

To quote @Tombart's answer

These limits will be applied after reboot.

If you want to apply changes without reboot, modify
/etc/pam.d/common-session by adding this line at the end of file:

session required pam_limits.so

share|improve this answer

edited Mar 20 '17 at 10:18

Community♦

1

answered Jul 5 '16 at 16:04

serv-incserv-inc

49422 silver badges1212 bronze badges

add a comment | 

protected by Community♦ Feb 22 '15 at 15:58

Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



Would you like to answer one of these unanswered questions instead?

105

No but you should close all active sessions windows. They still remember the old values. In other words, log out and back in.
Every remote new session or a local secure shell take effect of the limits changes.

share|improve this answer

edited Jan 2 '15 at 3:08

Gilles

569k136136 gold badges11741174 silver badges16861686 bronze badges

answered Jan 9 '14 at 19:02

SlyxSlyx

2,82722 gold badges1313 silver badges2424 bronze badges

• 
  
  
  

  
  17
  

  
  
  
  
  
  

  
  
  What if I want to set the limits for a user that doesn't have a login, like if I want to set the nofile limit to 94000 for the mongodb user? How'd I do that without a reboot? Would I just need to restart the mongodb service?
  
  – Alexej Magura
  Jan 9 '14 at 19:35
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  @AlexejMagura You can modify the the rlimits of running processes with the prlimit command.
  
  – Bratchley
  Jan 9 '14 at 23:46
  

  
  
  
  


• 
  
  
  

  
  7
  

  
  
  
  
  
  

  
  
  @Gilles, thanks for the precisions, I edited my answer to to avoid ambiguity. However Starting a new service using sudo service mongodb restart is enough to let the service running with the new limit values.
  
  – Slyx
  Jan 10 '14 at 15:01
  

  
  
  
  


• 
  
  
  

  
  6
  

  
  
  
  
  
  

  
  
  if you are using Ubuntu, and mongodb is started by upstart, then changing these limits will not affect mongodb. As upstart does not read /etc/security config bugs.launchpad.net/ubuntu/+source/upstart/+bug/938669 you must set limit stanza in its upstart config file.
  
  – HVNSweeting
  Jan 19 '15 at 3:22
  

  
  
  
  


• 
  
  
  

  
  5
  

  
  
  
  
  
  

  
  
  It's another issue. upstart by design ignores the limits set in /etc/security/limits.conf.
  
  – Slyx
  Jan 20 '15 at 11:00
  

  
  
  
  

add a comment | 

105

No but you should close all active sessions windows. They still remember the old values. In other words, log out and back in.
Every remote new session or a local secure shell take effect of the limits changes.

share|improve this answer

edited Jan 2 '15 at 3:08

Gilles

569k136136 gold badges11741174 silver badges16861686 bronze badges

answered Jan 9 '14 at 19:02

SlyxSlyx

2,82722 gold badges1313 silver badges2424 bronze badges

• 
  
  
  

  
  17
  

  
  
  
  
  
  

  
  
  What if I want to set the limits for a user that doesn't have a login, like if I want to set the nofile limit to 94000 for the mongodb user? How'd I do that without a reboot? Would I just need to restart the mongodb service?
  
  – Alexej Magura
  Jan 9 '14 at 19:35
  

  
  
  
  


• 
  
  
  

  
  2
  

  
  
  
  
  
  

  
  
  @AlexejMagura You can modify the the rlimits of running processes with the prlimit command.
  
  – Bratchley
  Jan 9 '14 at 23:46
  

  
  
  
  


• 
  
  
  

  
  7
  

  
  
  
  
  
  

  
  
  @Gilles, thanks for the precisions, I edited my answer to to avoid ambiguity. However Starting a new service using sudo service mongodb restart is enough to let the service running with the new limit values.
  
  – Slyx
  Jan 10 '14 at 15:01
  

  
  
  
  


• 
  
  
  

  
  6
  

  
  
  
  
  
  

  
  
  if you are using Ubuntu, and mongodb is started by upstart, then changing these limits will not affect mongodb. As upstart does not read /etc/security config bugs.launchpad.net/ubuntu/+source/upstart/+bug/938669 you must set limit stanza in its upstart config file.
  
  – HVNSweeting
  Jan 19 '15 at 3:22
  

  
  
  
  


• 
  
  
  

  
  5
  

  
  
  
  
  
  

  
  
  It's another issue. upstart by design ignores the limits set in /etc/security/limits.conf.
  
  – Slyx
  Jan 20 '15 at 11:00
  

  
  
  
  

add a comment | 

No but you should close all active sessions windows. They still remember the old values. In other words, log out and back in.
Every remote new session or a local secure shell take effect of the limits changes.

share|improve this answer

edited Jan 2 '15 at 3:08

Gilles

569k136136 gold badges11741174 silver badges16861686 bronze badges

answered Jan 9 '14 at 19:02

SlyxSlyx

2,82722 gold badges1313 silver badges2424 bronze badges

share|improve this answer

edited Jan 2 '15 at 3:08

Gilles

569k136136 gold badges11741174 silver badges16861686 bronze badges

answered Jan 9 '14 at 19:02

SlyxSlyx

2,82722 gold badges1313 silver badges2424 bronze badges

edited Jan 2 '15 at 3:08

Gilles

569k136136 gold badges11741174 silver badges16861686 bronze badges

edited Jan 2 '15 at 3:08

Gilles

569k136136 gold badges11741174 silver badges16861686 bronze badges

answered Jan 9 '14 at 19:02

SlyxSlyx

2,82722 gold badges1313 silver badges2424 bronze badges

answered Jan 9 '14 at 19:02

SlyxSlyx

2,82722 gold badges1313 silver badges2424 bronze badges

34

Apply the changes directly to a running process if you have prlimit installed (comes with util-linux-2.21)

prlimit --pid <pid> --<limit>=<soft>:<hard>

for example

prlimit --pid 12345 --nofile=1024:2048

Refer here

share|improve this answer

answered Apr 6 '15 at 10:21

RamRam

63122 gold badges1111 silver badges1818 bronze badges

add a comment | 

34

Apply the changes directly to a running process if you have prlimit installed (comes with util-linux-2.21)

prlimit --pid <pid> --<limit>=<soft>:<hard>

for example

prlimit --pid 12345 --nofile=1024:2048

Refer here

share|improve this answer

answered Apr 6 '15 at 10:21

RamRam

63122 gold badges1111 silver badges1818 bronze badges

add a comment | 

Apply the changes directly to a running process if you have prlimit installed (comes with util-linux-2.21)

prlimit --pid <pid> --<limit>=<soft>:<hard>

for example

prlimit --pid 12345 --nofile=1024:2048

Refer here

share|improve this answer

answered Apr 6 '15 at 10:21

RamRam

63122 gold badges1111 silver badges1818 bronze badges

prlimit --pid <pid> --<limit>=<soft>:<hard>

prlimit --pid 12345 --nofile=1024:2048

share|improve this answer

answered Apr 6 '15 at 10:21

RamRam

63122 gold badges1111 silver badges1818 bronze badges

answered Apr 6 '15 at 10:21

RamRam

63122 gold badges1111 silver badges1818 bronze badges

answered Apr 6 '15 at 10:21

RamRam

63122 gold badges1111 silver badges1818 bronze badges

29

To temporarily set the open files limit for the user you are currently logged in under (e.g. 'root'):You can also use the ulimit command to change the values in your current shell. However, hard limits can only be adjusted downwards unless you're root.

Example:

# ulimit -a

core file size          (blocks, -c) 0

data seg size           (kbytes, -d) unlimited

scheduling priority             (-e) 0

file size               (blocks, -f) unlimited

pending signals                 (-i) 62449

max locked memory       (kbytes, -l) 64

max memory size         (kbytes, -m) unlimited

open files                      (-n) 1024

pipe size            (512 bytes, -p) 8

POSIX message queues     (bytes, -q) 819200

real-time priority              (-r) 0

stack size              (kbytes, -s) 10240

cpu time               (seconds, -t) unlimited

max user processes              (-u) 1024

virtual memory          (kbytes, -v) unlimited

file locks                      (-x) unlimited

To change the nofile to 94000 you can do:

ulimit -n 94000

share|improve this answer

edited May 25 '17 at 10:59

Community♦

1

answered Jan 10 '14 at 8:44

BoogyBoogy

81866 silver badges88 bronze badges

add a comment | 

29

To temporarily set the open files limit for the user you are currently logged in under (e.g. 'root'):You can also use the ulimit command to change the values in your current shell. However, hard limits can only be adjusted downwards unless you're root.

Example:

# ulimit -a

core file size          (blocks, -c) 0

data seg size           (kbytes, -d) unlimited

scheduling priority             (-e) 0

file size               (blocks, -f) unlimited

pending signals                 (-i) 62449

max locked memory       (kbytes, -l) 64

max memory size         (kbytes, -m) unlimited

open files                      (-n) 1024

pipe size            (512 bytes, -p) 8

POSIX message queues     (bytes, -q) 819200

real-time priority              (-r) 0

stack size              (kbytes, -s) 10240

cpu time               (seconds, -t) unlimited

max user processes              (-u) 1024

virtual memory          (kbytes, -v) unlimited

file locks                      (-x) unlimited

To change the nofile to 94000 you can do:

ulimit -n 94000

share|improve this answer

edited May 25 '17 at 10:59

Community♦

1

answered Jan 10 '14 at 8:44

BoogyBoogy

81866 silver badges88 bronze badges

add a comment | 

To temporarily set the open files limit for the user you are currently logged in under (e.g. 'root'):You can also use the ulimit command to change the values in your current shell. However, hard limits can only be adjusted downwards unless you're root.

Example:

# ulimit -a

core file size          (blocks, -c) 0

data seg size           (kbytes, -d) unlimited

scheduling priority             (-e) 0

file size               (blocks, -f) unlimited

pending signals                 (-i) 62449

max locked memory       (kbytes, -l) 64

max memory size         (kbytes, -m) unlimited

open files                      (-n) 1024

pipe size            (512 bytes, -p) 8

POSIX message queues     (bytes, -q) 819200

real-time priority              (-r) 0

stack size              (kbytes, -s) 10240

cpu time               (seconds, -t) unlimited

max user processes              (-u) 1024

virtual memory          (kbytes, -v) unlimited

file locks                      (-x) unlimited

To change the nofile to 94000 you can do:

ulimit -n 94000

share|improve this answer

edited May 25 '17 at 10:59

Community♦

1

answered Jan 10 '14 at 8:44

BoogyBoogy

81866 silver badges88 bronze badges

# ulimit -a

core file size          (blocks, -c) 0

data seg size           (kbytes, -d) unlimited

scheduling priority             (-e) 0

file size               (blocks, -f) unlimited

pending signals                 (-i) 62449

max locked memory       (kbytes, -l) 64

max memory size         (kbytes, -m) unlimited

open files                      (-n) 1024

pipe size            (512 bytes, -p) 8

POSIX message queues     (bytes, -q) 819200

real-time priority              (-r) 0

stack size              (kbytes, -s) 10240

cpu time               (seconds, -t) unlimited

max user processes              (-u) 1024

virtual memory          (kbytes, -v) unlimited

file locks                      (-x) unlimited

ulimit -n 94000

share|improve this answer

edited May 25 '17 at 10:59

Community♦

1

answered Jan 10 '14 at 8:44

BoogyBoogy

81866 silver badges88 bronze badges

edited May 25 '17 at 10:59

Community♦

1

edited May 25 '17 at 10:59

Community♦

1

answered Jan 10 '14 at 8:44

BoogyBoogy

81866 silver badges88 bronze badges

answered Jan 10 '14 at 8:44

BoogyBoogy

81866 silver badges88 bronze badges

14

Limits are inherited from a parent process to its child processes. Processes running as root can change limits arbitrarily; other processes cannot increase hard limits. Thus the hard limits set by the login process affect all the processes in a session.

If you change /etc/security/limits.conf, this will affect all new sessions, and processes in these new sessions. It won't affect processes that are already running, nor processes started by processes that are already running.

So if you need to increase some limits, you'll have to either log out and back in, or start another session (e.g. with ssh localhost, or on another console).

share|improve this answer

answered Jan 10 '14 at 2:29

GillesGilles

569k136136 gold badges11741174 silver badges16861686 bronze badges

add a comment | 

14

Limits are inherited from a parent process to its child processes. Processes running as root can change limits arbitrarily; other processes cannot increase hard limits. Thus the hard limits set by the login process affect all the processes in a session.

If you change /etc/security/limits.conf, this will affect all new sessions, and processes in these new sessions. It won't affect processes that are already running, nor processes started by processes that are already running.

So if you need to increase some limits, you'll have to either log out and back in, or start another session (e.g. with ssh localhost, or on another console).

share|improve this answer

answered Jan 10 '14 at 2:29

GillesGilles

569k136136 gold badges11741174 silver badges16861686 bronze badges

add a comment | 

Limits are inherited from a parent process to its child processes. Processes running as root can change limits arbitrarily; other processes cannot increase hard limits. Thus the hard limits set by the login process affect all the processes in a session.

If you change /etc/security/limits.conf, this will affect all new sessions, and processes in these new sessions. It won't affect processes that are already running, nor processes started by processes that are already running.

So if you need to increase some limits, you'll have to either log out and back in, or start another session (e.g. with ssh localhost, or on another console).

share|improve this answer

answered Jan 10 '14 at 2:29

GillesGilles

569k136136 gold badges11741174 silver badges16861686 bronze badges

share|improve this answer

answered Jan 10 '14 at 2:29

GillesGilles

569k136136 gold badges11741174 silver badges16861686 bronze badges

answered Jan 10 '14 at 2:29

GillesGilles

569k136136 gold badges11741174 silver badges16861686 bronze badges

answered Jan 10 '14 at 2:29

GillesGilles

569k136136 gold badges11741174 silver badges16861686 bronze badges

4

To quote @Tombart's answer

These limits will be applied after reboot.

If you want to apply changes without reboot, modify
/etc/pam.d/common-session by adding this line at the end of file:

session required pam_limits.so

share|improve this answer

edited Mar 20 '17 at 10:18

Community♦

1

answered Jul 5 '16 at 16:04

serv-incserv-inc

49422 silver badges1212 bronze badges

add a comment | 

4

To quote @Tombart's answer

These limits will be applied after reboot.

If you want to apply changes without reboot, modify
/etc/pam.d/common-session by adding this line at the end of file:

session required pam_limits.so

share|improve this answer

edited Mar 20 '17 at 10:18

Community♦

1

answered Jul 5 '16 at 16:04

serv-incserv-inc

49422 silver badges1212 bronze badges

add a comment | 

To quote @Tombart's answer

These limits will be applied after reboot.

If you want to apply changes without reboot, modify
/etc/pam.d/common-session by adding this line at the end of file:

session required pam_limits.so

share|improve this answer

edited Mar 20 '17 at 10:18

Community♦

1

answered Jul 5 '16 at 16:04

serv-incserv-inc

49422 silver badges1212 bronze badges

share|improve this answer

edited Mar 20 '17 at 10:18

Community♦

1

answered Jul 5 '16 at 16:04

serv-incserv-inc

49422 silver badges1212 bronze badges

edited Mar 20 '17 at 10:18

Community♦

1

edited Mar 20 '17 at 10:18

Community♦

1

answered Jul 5 '16 at 16:04

serv-incserv-inc

49422 silver badges1212 bronze badges

answered Jul 5 '16 at 16:04

serv-incserv-inc

49422 silver badges1212 bronze badges