search for: ncessair

...-> ../sysctl.conf # yum provides /etc/sysctl.d/99-sysctl.conf initscripts-9.49.30-1.el7.x86_64 : The inittab file and the /etc/init.d scripts D?p?t : base Correspondance depuis : Nom de fichier : /etc/sysctl.d/99-sysctl.conf Sylvain. Pensez ENVIRONNEMENT : n'imprimer que si ncessaire

...FreeBSD, NetBSD, OpenBSD will be much smaller step than stepping up to CentOS 7 - that is my experience, though FreeBSD migration of servers I started came much earlier than CentOS 7 and for different reason). Good Luck! Valeri > > Sylvain. > Pensez ENVIRONNEMENT : n'imprimer que si ncessaire > +++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++

...s out that way > for you as a systemctl cat NetworkManager indicates it should be before > network and it looks like it may block progress until it's on dbus ... Ok, I'll try, and see if that solves my problem. Thank you. Sylvain CANOINE. Pensez ENVIRONNEMENT : n'imprimer que si ncessaire

...k Loaded: loaded (/usr/lib/systemd/system/network.target; static; vendor preset: disabled) Active: inactive (dead) Docs: man:systemd.special(7) http://www.freedesktop.org/wiki/Software/systemd/NetworkTarget Dead ? Hmmm... Sylvain. Pensez ENVIRONNEMENT : n'imprimer que si ncessaire

...er.org/iptables.man.html), not specifying "-p" is equivalent to specifying "-p all", which matches with all protocols, icmp included. So these rules are good. BUT... I suppose /bin/ping has a suid bit set, no ? > > Sylvain. > Pensez ENVIRONNEMENT : n'imprimer que si ncessaire Blocking the complete ICMP protocol is stupid and should not be recommended. ICMP echo request and echo reply are just 2 types of a bigger set of necessary ICMP types. It is safe to block those 2 while that does not really serve a purpose. A system not replying on ICMP echo request does not h...

Hello, Is it possible at all to block all users other than root from sending outbound ICMP packets on an interface? At the moment we have the following two rules in our IPtables config: iptables -A OUTPUT -o eth1 -m owner --uid-owner 0 -j ACCEPT iptables -A OUTPUT -o eth1 -j DROP But this still allows ICMP for some reason (but *does* block other TCP/UDP packets, which is what we want, as well

On CentOS release 6.7, there's file system problem. Aftert reboot /home is set under /home (/home/home) like followings. # ls -l /home total 48 -rw------- 1 root root 7168 Nov 15 19:10 aquota.group -rw------- 1 root root 7168 Jan 25 11:09 aquota.user drwxr-x--- 2 root root 4096 Jan 18 21:55 backups drwxr-xr-x 4 root root 4096 Jan 1 11:59 home drwxr-xr-x 8 root root 4096 Apr 5

...753]: Activation de l'interface ens160 : [ OK ] d?c. 22 17:42:15 (correct) network[753]: Activation de l'interface ens192 : [ OK ] d?c. 22 17:42:15 (correct) systemd[1]: Started LSB: Bring up/down networking. To be continued... Sylvain. Pensez ENVIRONNEMENT : n'imprimer que si ncessaire

On Jan 24, 2016, at 6:40 PM, Peter Duffy <peter at pwduffy.org.uk> wrote: > The thing which always gets me about systemd is not the thing itself, > but the way it was rolled out. When I first installed Red Hat 7, if a > window had appeared telling me about systemd and asking me if I wanted > to use it, or stick with the old init framework, I'd have opted for the > latter

...s changing its settings, needs D-bus just to work, so it is too much complex just to set static IP addresses on network interfaces. They said multiples administrator actions, and potentially human errors, to set it up, may be a security risk... Sylvain. Pensez ENVIRONNEMENT : n'imprimer que si ncessaire

...nline.target's unit. I chose another solution : I made a symlink to /usr/lib/systemd/system/network/target in /etc/systemd/system/multi-user.target.wants/ directory ("systemctl enable network.target" sent me to hell). And voil?. Sylvain. Pensez ENVIRONNEMENT : n'imprimer que si ncessaire

On 12/23/2015 11:12 PM, Ofer Hasson wrote: > [root at web-devel-local-1 ~]# /usr/lib/systemd/systemd-sysctl > [root at web-devel-local-1 ~]# cat /proc/sys/vm/swappiness > 10 So... you know that it works when you run it from a root shell, but not during boot. Is the file labeled properly? Anything in audit.log?

On 12/23/2015 08:38 AM, Sylvain CANOINE wrote: > Then I'm wondering : > 2/ why "After=foo" does not imply "Requires=foo" for systemd 219, while it appeared to be in systemd 208. Either it's a regression, or the behaviour of 208, although logical, is buggy. I'm not entirely certain, but "After=" is independent of "Requires=", as documented

I'm only getting a text console with CentOS-7.2 on my (oldish) HP MicroServer. The only explicit error I see in Xorg.0.log is that no driver is found for my Pixart USB optical mouse. My query is: would that be sufficient to prevent a graphic console? Incidentally, I can use X apps, eg xpdf, if I ssh in from my laptop. As always, any advice gratefully received. -- Timothy Murphy

...dev" > (II) evdev: Power Button: Close > (II) UnloadModule: "evdev" > (II) Server terminated successfully (0). Closing log file. As these logs have "info" level (II), there is no real problem for xorg. Sylvain CANOINE. Pensez ENVIRONNEMENT : n'imprimer que si ncessaire

...sysctl.d/99-sysctl.conf > initscripts-9.49.30-1.el7.x86_64 : The inittab file and the /etc/init.d > scripts > D?p?t : base > Correspondance depuis : > Nom de fichier : /etc/sysctl.d/99-sysctl.conf > > > Sylvain. > Pensez ENVIRONNEMENT : n'imprimer que si ncessaire > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos >

I have a gst-rtsp-server 0.10.8.2 that I am trying to compile on CentOS 7.2 I get this error: rtsp-media.c error 'g_cond_free' is deprecated (declared at /usr/include/glib-2.0/glib/deprecated/gthread.h:283) [-Werror=deprecated-declarations] What can I do about that to compile this package (I'm compiing from source) ? Thanks Jerry

...ing, and why RedHat/CentOS maintainers dismiss this fact (the CentOS 7.1 to 7.2 update is painful, because systemd switched from 208 to 219) ? Why, more generally, the answer is often "systemd" when I encounter a problem on a server ? Sylvain. Pensez ENVIRONNEMENT : n'imprimer que si ncessaire

...etter". > > https://wiki.debian.org/Debate/initsystem/systemd#Why_Debian_should_default_to_systemd > Counter-arguments are easy to find as well. For example : http://judecnelson.blogspot.fr/2014/09/systemd-biggest-fallacies.html Sylvain. Pensez ENVIRONNEMENT : n'imprimer que si ncessaire

...follow. Ubuntu and Debian choose systemd, on one hand, because more and more softs depend on systemd (Gnome 3, for example), and on the other hand, to save maintainers time, dropping their own init system. The technically best choice, you say ? Sylvain. Pensez ENVIRONNEMENT : n'imprimer que si ncessaire