On Sat, Oct 24, 2015 at 11:05:50PM +0200, Tobias Hunger wrote:
> Hi Systemd List!
>
> I have been trying today to pass some information into a container I
> set up with systemd-nspawn, using --setenv=SOMEVAR=foo. That works, I
> see SOMEVAR in /proc/1/environ of the container.
>
> So far so good.
Hi Systemd List!
I have been trying today to pass some information into a container I
set up with systemd-nspawn, using --setenv=SOMEVAR=foo. That works, I
see SOMEVAR in /proc/1/environ of the container.
So far so good.
Now I want to use that information to configure a service, so I add a
scrip
Hello!
There is one more question I try to get a clearness for myself -- direct
systemd-journald event-logs tranmssion to Zabbix\Cacti\other log-collector.
As I understand nowadays we have such event-logs tranmssion schemas:
Windows OS system:
| Win System | -->|EventLog-To-Syslog Service| -->
The 1984 big brother interface systemd for totalitarian control
of all aspects of digitial life of the users and their devices
is doomed to fail.
This can only be a project of the NSA sickos.
systemd must be destroyed.
___
systemd-devel mailing list
sys
well, you can argue with all sorts of workarounds, lacking something
like specify a port for a tcp connection is a fractal of bad design
Am 24.10.2015 um 16:58 schrieb Andy Pieters:
Exactly so for Reindl's use scenario, considering 5 hosts all on the
same ip address but with different ports, c
24.10.2015 16:57, Reindl Harald пишет:
Am 24.10.2015 um 15:04 schrieb Lennart Poettering:
Well, I am pretty sure using "#" as separator for that is a really
untypical syntax. I am not sure it's really such a big improvement
supporting such a syntax over simply asking people to put the right
sta
Am 24.10.2015 um 15:04 schrieb Lennart Poettering:
Well, I am pretty sure using "#" as separator for that is a really
untypical syntax. I am not sure it's really such a big improvement
supporting such a syntax over simply asking people to put the right
statement in ~/.ssh/config... Note thta the
On Sat, 24.10.15 09:20, Stuart Longland (stua...@longlandclan.id.au) wrote:
> Makes sense. So that explains why not another character such as /. I
> suppose # might work as a delimiter for specifying a port number:
>
> e.g.
> foo#portno
>
> I seem to recall seeing that in BIND:
> > 24-Oc
On Fri, 23.10.15 17:50, Daniel Brown (daniel.br...@dart.biz) wrote:
> Hi all,
>
> I am getting some core dumps when I am running the timedatectl
> command. I am using 32 bit iso in qemu and I can only reproduce the
> error when I set the vm to this particular mac address
> fe:f1:f0:61:1f:55 . Her
