> Thanks, I did know that and we are using this in other situations. But
> as written in my third reply:
>
> To much work every MAC I dont have to type counts.
Take some time to write a script, and you'll earn much time after. But it's a
really, really bad idea to configure too long leases.
Syl
- Mail original -
> De: "望月忠雄"
> À: "centos"
> Envoyé: Mardi 12 Avril 2016 08:17:13
> Objet: [CentOS] mount bind problem
> I have set on fstab /home with 'mount bind' but it seems like bind is not
> effective.
Indeed. By default, nothing mounts "bind" filesystems. The init scripts don'
- Mail original -
> De: "Stefan Fuhrmann"
> À: "centos"
> Envoyé: Jeudi 7 Avril 2016 16:13:26
> Objet: [CentOS] centos samba sssd active directory
> Hello all,
> Im having the latest centos that should be integrated into win 2012 active
> directory domain.
> Im having Authentication ru
- Mail original -
> De: "g"
> À: "centos"
> Envoyé: Jeudi 3 Mars 2016 23:46:10
> Objet: [CentOS] 6.7 netinstall fails at insert cd to continue
> system: hp compact dc7800 dual 64 bit
> cd/dvd: oem sata-- recognized as
> atapi dvd c dh48c2s sat
Hello,
- Mail original -
> De: "John Cenile"
> À: "centos"
> 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 mo
> De: "Ricardo J. Barberis"
> [Unit]
> After=network.target remote-fs.target nss-lookup.target network-online.target
>
>
>
> The After line is the important one, I copied it from
> /usr/lib/systemd/system/nginx.service and added "network-online.target"
> at the end.
>
> After making your chang
>> Jonathan Billings wrote:
>>
>> >> > 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.
>>
>> > I suggest reading the p
- Mail original -
> De: "Jonathan Billings"
> 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 q
> * 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
> Ultimately it's all software, and software can be
> written/changed/updated to do anything required - all that's needed is
> the skill and the motivation. If systemd is so "core" that it can't be
> unplugged and plugged easily, and glues together a lot of otherwise
> unrelated components, then i
>> 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-f
> If that is the case, why do you run CentOS 7 on the server? You can stay
> with CentOS 6 for now and either wait till Linux systemd-free distribution
> mature enough to be run on server is available. Which it almost is: Devuan
> (systemd-free fork of Debian) has released "alpha" version about ha
> 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
com
>
> ??
>
>>
>>> If I change the zone defs to include the full path:
>>>
>>> From
>>>
>>> zone "relationships123.com." IN {
>>> type master;
>>> file "relationships123.com.d
II) evdev: Power Button: Close
> (II) UnloadModule: "evdev"
> (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.
S
X refuses to start because of missing
or inappropriate video drivers.
Next in the other discussion thread...
Sylvain CANOINE.
Pensez ENVIRONNEMENT : n'imprimer que si ncessaire
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
- Mail original -
> De: "Ofer Hasson"
> À: "centos"
> Envoyé: Jeudi 24 Décembre 2015 11:36:00
> Objet: Re: [CentOS] systemd-sysctl not running on boot
> [root@web-devel-local-1 ~]# ll -Z /etc/ | grep sysctl
> drwxr-xr-x. root root system_u:object_r:etc_t:s0 sysctl.d
>
> [root
- Mail original -
> De: "Gordon Messmer"
> À: "centos"
> Envoyé: Jeudi 24 Décembre 2015 07:25:00
> Objet: Re: [CentOS] Network services start before network is up since
> migrating to 7.2
> On 12/23/2015 08:38 AM, Sylvain CANOINE wrote:
>&g
- Mail original -
> De: "Sylvain CANOINE"
> À: "centos"
> 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
> ● netwo
- Mail original -
> De: "Gordon Messmer"
> À: "centos"
> 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 "net
- Mail original -
> De: "Gordon Messmer"
> À: "centos"
> Envoyé: Vendredi 18 Décembre 2015 12:06:26
> Objet: Re: [CentOS] Network services start before network is up since
> migrating to 7.2
>>> The network service is not blocking the flow so it executes and systemd
>>> carries on ...
- Mail original -
> De: "Marcelo Ricardo Leitner"
> À: "centos"
> 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 i
> 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 req
r
> system to see if it's a race condition or it actually works 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.
online.target" is the failing services' units, but I want to
understand what is the root problem, and what is the difference between my two
servers... And by now, I found nothing.
Got an idea ?
Sylvain CANOINE.
Pensez ENVIRONNEMENT : n'imprimer que si ncessaire
25 matches
Mail list logo
