Actually branch is not missing, User error.
But, there appears to be something else whther it's a kernel interface
error as proposed in the bug or something else.
Tony
On May 9, 2013 7:13 AM, "Tony Su" wrote:
> Thx all.
> After being being pointed to systemd-sysctrl.service, I was able to find
Thx all.
After being being pointed to systemd-sysctrl.service, I was able to find
this bug which was opened/closed/re-discussed/unresolved but the bug was
left "closed" which likely means it got lost
Http://bugzilla.redhat.com/show_bug.cgi?id=850427
I'll re-open in my distro's bugzilla.
The curio
On 08.05.2013 18:44, T.C. Hollingsworth wrote:
…
> systemd's involvement with /proc begins and ends with mounting it.
> The kernel defines its contents and they will be the same regardless
> of which init system you use.
…
cat /usr/lib/systemd/system/systemd-sysctl.service :)
poma
--
users m
On 05/08/2013 05:44 PM, T.C. Hollingsworth wrote:
On Wed, May 8, 2013 at 9:33 AM, Tony Su wrote:
In the "old days" edits were made directly to the appropriate file
/proc/net/ipv4/...
Are you looking for /proc/sys/net/ip4? AFAICT /proc/net hasn't
existed since everyone switched over to the 2.
On Wed, May 8, 2013 at 9:33 AM, Tony Su wrote:
> In the "old days" edits were made directly to the appropriate file
> /proc/net/ipv4/...
Are you looking for /proc/sys/net/ip4? AFAICT /proc/net hasn't
existed since everyone switched over to the 2.6 kernel (which happened
in Fedora Core 2 in 2004)
In the "old days" edits were made directly to the appropriate file
/proc/net/ipv4/...
With current systemd (running systemd v202), the entire IPv4 branch
appears to have been replaced.
Need guidance
- How to configure/re-configure the TCP/IP Congestion Control algorithm
- How to specify custom va
