search for: tv5monde

> If you're using NetworkManager, you can "systemctl enable > NetworkManager-wait-online.service" and you won't have to override any > of the individual services. Our security experts don't want me to use NetworkManager... It's even uninstalled on the models, so I understand better why all the required files are not here : # systemctl status

Em 21-12-2015 14:24, James Hogarth escreveu: > On 21 December 2015 at 15:08, Sylvain CANOINE <sylvain.canoine at tv5monde.org> > wrote: > >>> If you're using NetworkManager, you can "systemctl enable >>> NetworkManager-wait-online.service" and you won't have to override any >>> of the individual services. >> Our security experts don't want me to use Netwo...

On 22 December 2015 at 10:33, Sylvain CANOINE <sylvain.canoine at tv5monde.org> wrote: > > ----- Mail original ----- > > De: "Marcelo Ricardo Leitner" <marcelo.leitner at gmail.com> > > ?: "centos" <centos at centos.org> > > Envoy?: Lundi 21 D?cembre 2015 21:46:10 > > Objet: Re: [CentOS] Network services st...

On 21 December 2015 at 15:08, Sylvain CANOINE <sylvain.canoine at tv5monde.org> wrote: > > If you're using NetworkManager, you can "systemctl enable > > NetworkManager-wait-online.service" and you won't have to override any > > of the individual services. > Our security experts don't want me to use NetworkManager... It's...

James Hogarth wrote: > On 22 December 2015 at 10:33, Sylvain CANOINE > <sylvain.canoine at tv5monde.org> wrote: >> > De: "Marcelo Ricardo Leitner" <marcelo.leitner at gmail.com> <snip> >> In short, "you don't need it, so don't use it". >> They said NM is more a desktop-oriented tool, already had privilege >> escalation issues i...

----- Mail original ----- > De: "Sylvain CANOINE" <sylvain.canoine at tv5monde.org> > ?: "centos" <centos at centos.org> > Envoy?: Mercredi 23 D?cembre 2015 12:26:39 > Objet: Re: [CentOS] Network services start before network is up since migrating to 7.2 > > # systemctl status network.target > ? network.target - Network > Loaded: loa...

I dont see any reason this will have anything to do with the issue. In any case, i re-installed the package, had the symlink, moved my definitions to sysctl.conf. still the same.... On Mon, Dec 28, 2015 at 1:17 PM, Sylvain CANOINE < sylvain.canoine at tv5monde.org> wrote: > > ----- Mail original ----- > > De: "Ofer Hasson" <hassonofer at gmail.com> > > ?: "centos" <centos at centos.org> > > Envoy?: Jeudi 24 D?cembre 2015 11:36:00 > > Objet: Re: [CentOS] systemd-sysctl not running on boot &...

----- Mail original ----- > De: "Ofer Hasson" <hassonofer at gmail.com> > ?: "centos" <centos at centos.org> > Envoy?: Jeudi 24 D?cembre 2015 11:36:00 > Objet: Re: [CentOS] systemd-sysctl not running on boot > [root at web-devel-local-1 ~]# ll -Z /etc/ | grep sysctl > drwxr-xr-x. root root system_u:object_r:etc_t:s0 sysctl.d > >

----- Mail original ----- > De: "Gordon Messmer" <gordon.messmer at gmail.com> > ?: "centos" <centos at centos.org> > Envoy?: Mercredi 23 D?cembre 2015 10:11:05 > Objet: Re: [CentOS] Network services start before network is up since migrating to 7.2 > I'm a little confused, too. But, it might be more informative to query > the system for

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

On Tue, Jan 26, 2016 at 11:51:29AM +0000, Peter Duffy wrote: > I'm also still trying to figure out in what way systemd is supposed to > be "better". I've seen the following things claimed for it: Of the three things you list, hot-plug is certainly an important one. But, it's not the big deal. The big deal is that systemd is not just a fire-and-hope startup system, but

On 17 December 2015 at 11:12, Sylvain CANOINE <sylvain.canoine at tv5monde.org> wrote: > Hello all, > > I updated two of my servers to CentOS 7.2 (1511) two days ago, and since, > on one of them, the network services are started (and fail to start) before > the network interfaces are online. > > Parts of "journalctl" after the last reboo...

Hello all, I updated two of my servers to CentOS 7.2 (1511) two days ago, and since, on one of them, the network services are started (and fail to start) before the network interfaces are online. Parts of "journalctl" after the last reboot : d?c. 17 10:21:44 myserver kernel: NET: Registered protocol family 40 d?c. 17 10:21:45 myserver sshd[700]: error: Bind to port 22 on

----- Mail original ----- > De: "Marcelo Ricardo Leitner" <marcelo.leitner at gmail.com> > ?: "centos" <centos at centos.org> > Envoy?: Lundi 21 D?cembre 2015 21:46:10 > Objet: Re: [CentOS] Network services start before network is up since migrating to 7.2 > Agreed. Sylvain, if possible, please elaborate on their reasoning for > this, because it

> No error is given in /var/log/Xorg.0.log. > It seems to find an appropriate ATI Radeon driver, > but it has the warnings > (WW) Falling back to old probe method for modesetting > (WW) Falling back to old probe method for fbdev > (WW) Falling back to old probe method for vesa Could you share your whole Xorg.0.log ? Do you use a custom xorg.conf, or custom xorg.conf.d files ?

> I believe that RHEL7 (and CentOS7) both have systemd integrated into them enough > that it isn?t as simple as ?choose init system? on install. That's because of systemd. Even if most of the linux distros don't, giving the choice is a bit less difficult with any other init system. The main problem is systemd makes (often badly) more and more things that, as a "simple"

>> I'm also still trying to figure out in what way systemd is supposed to >> be "better". > > 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

> * insure that when something is stopped, it's actually stopped. (If > you've ever managed an HPC cluster and had processes escape the > scheduler, you know this problem is real.) # systemctl list-units | grep -c abandoned 453 # uptime 15:53:58 up 11 days, 21:03, 1 user, load average, 0,01, 0,02, 0,05 > > * track process lifecycle, and restart (or take other

----- Mail original ----- > De: "Jonathan Billings" <billings at negate.org> > Maybe you're not aware of it, but there are a LOT of things that > systemd fixes that people are happy about. Like what ? I don't remember there were as many errors to fix before systemd appeared. Sylvain. Pensez ENVIRONNEMENT : n'imprimer que si ncessaire

Hello, ----- Mail original ----- > De: "John Cenile" <jcenile1983 at gmail.com> > ?: "centos" <centos at centos.org> > Envoy?: Mercredi 24 F?vrier 2016 15:42:36 > Objet: [CentOS] IPtables block user from outbound ICMP > Is it possible at all to block all users other than root from sending > outbound ICMP packets on an interface? > > At the