Am 2015-07-27 12:31, schrieb John Lane:
I have a problem with what I thought would be a simple service unit:
# /etc/systemd/system/socat.service
[Service]
ExecStart=/usr/bin/socat UDP-RECV:4321 STDOUT
The expected outcome is that /usr/bin/socat UDP-RECV:4321 STDOUT is
started with
Try using `socat -u` for unidirectional mode.
Yes that was it. Thank you.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Mon, 27.07.15 11:31, John Lane (syst...@jelmail.com) wrote:
I have a problem with what I thought would be a simple service unit:
# /etc/systemd/system/socat.service
[Service]
ExecStart=/usr/bin/socat UDP-RECV:4321 STDOUT
The expected outcome is that /usr/bin/socat
On Mon, Jul 27, 2015 at 1:31 PM, John Lane syst...@jelmail.com wrote:
I have a problem with what I thought would be a simple service unit:
# /etc/systemd/system/socat.service
[Service]
ExecStart=/usr/bin/socat UDP-RECV:4321 STDOUT
The expected outcome is that /usr/bin/socat
Hi,
is there anything in systemd what somehow manipulate $PATH.
I am asking because of:
https://bugzilla.redhat.com/show_bug.cgi?id=1246810
which claims that when run as
systemd --user
it gets /usr/sbin at the begging of $PATH.
And I have no idea how can I run systemd --user command so I can
On Mon, Jul 27, 2015 at 02:15:31PM +0200, Miroslav Suchý wrote:
Hi,
is there anything in systemd what somehow manipulate $PATH.
Systemd sets $PATH to a fixed value for services[1], with /sbin before
/bin. But this shouldn't normally be visible in a user shell, unless
it is run directly as a
On Sat, 25.07.15 08:11, SF Markus Elfring (elfr...@users.sourceforge.net) wrote:
I am sorry Markus, but at this point you are just wasting our time. Be
specific (i.e. by sending git patches, providing backtraces of
crashes, or actual bug reports), otherwise this is of no help. I will
now stop
On Mon, 27 Jul 2015 16:51:02 +0200, Lennart Poettering wrote:
Coming back to your original question, there are two options:
1) nfs-common becomes a normal multi-user.target service, but adds
Before=remote-fs-pre.target. This way, the service is started at
boot, and not only on first
On Sun, 26.07.15 00:08, Andrei Borzenkov (arvidj...@gmail.com) wrote:
В Sat, 25 Jul 2015 12:50:39 +0200
Michael Biebl mbi...@gmail.com пишет:
2015-07-25 3:18 GMT+02:00 Rich Freeman r-syst...@thefreemanclan.net:
I noticed that mount units for nfs shares created by the generator do
not
On Mon, 27.07.15 01:18, Christopher Cox (c...@endlessnow.com) wrote:
I suspect that somebody here knows why, but all mounts now fail... well all
but /.
Has anyone run across this before? What did I miss?
I accidentally messed up my boot mbr. and I did a rescue cd and chroot in
order to
On Sat, 25.07.15 18:11, SF Markus Elfring (elfr...@users.sourceforge.net) wrote:
Hello,
I would like to clarify the setting of device file permissions
for my needs.
So I extended the debug output at some source code places to see
also better which lines are executed during my tests.
I
On Mon, 27.07.15 15:19, Felipe Sateler (fsate...@debian.org) wrote:
On Mon, 27 Jul 2015 16:51:02 +0200, Lennart Poettering wrote:
Coming back to your original question, there are two options:
1) nfs-common becomes a normal multi-user.target service, but adds
On Sun, 26.07.15 11:39, Oleksii Shevchuk (alx...@gmail.com) wrote:
Andrei Borzenkov arvidj...@gmail.com writes:
Could you verify with e.g. inotifywatch whether inotify event was
generated by kernel?
It turns out, that for some reason I have several dm devices:
# ls -l
On Thu, 16.07.15 20:22, Thomas Meyer (tho...@m3y3r.de) wrote:
diff --git a/rules/60-persistent-storage.rules
b/rules/60-persistent-storage.rules
index 5ab03fc..0b14bb4 100644
--- a/rules/60-persistent-storage.rules
+++ b/rules/60-persistent-storage.rules
@@ -6,7 +6,7 @@
ACTION==remove,
On Mon, 27.07.15 13:25, Rich Freeman (r-syst...@thefreemanclan.net) wrote:
On Mon, Jul 27, 2015 at 10:51 AM, Lennart Poettering
lenn...@poettering.net wrote:
If you are looking for a way to start this service only when an NFS
mount is attempted, then I must disappoint you: there's
On Fri, 17.07.15 10:22, Ben Gamari (b...@smart-cactus.org) wrote:
I have been having quite some trouble getting nspawn give me a shell
with proper job control in a CentOS 6.6 guest. The problem appears to be
that the nodes representing the std{out,err,in} fds in /proc are
malformed,
Hmm,
On Mon, Jul 27, 2015 at 10:51 AM, Lennart Poettering
lenn...@poettering.net wrote:
If you are looking for a way to start this service only when an NFS
mount is attempted, then I must disappoint you: there's currently no
way to do this nicely, as you can neither express applies only to
NFS,
On Mon, 27.07.15 17:52, Keller, Jacob E (jacob.e.kel...@intel.com) wrote:
Hello,
I am working with a network device that can create virtual function
devices. When I create a large (8) vfs for this device I get some
weird device names,
Not sure I fully grok, but is this about SR-IOV?
ens8
В Mon, 27 Jul 2015 17:52:59 +
Keller, Jacob E jacob.e.kel...@intel.com пишет:
Hello,
I am working with a network device that can create virtual function
devices. When I create a large (8) vfs for this device I get some
weird device names,
If I create 64 vfs, I see something like:
On Mon, 2015-07-27 at 21:12 +0300, Andrei Borzenkov wrote:
В Mon, 27 Jul 2015 17:52:59 +
Keller, Jacob E jacob.e.kel...@intel.com пишет:
Hello,
I am working with a network device that can create virtual function
devices. When I create a large (8) vfs for this device I get some
Hello,
I am working with a network device that can create virtual function
devices. When I create a large (8) vfs for this device I get some
weird device names,
If I create 64 vfs, I see something like:
ens8
ens8f[1-7]
ens8s[1-7]
enp8s[1-7]f[1-7]
If I create 64 vfs, I see something like:
where
On Mon, 2015-07-27 at 20:05 +0200, Lennart Poettering wrote:
On Mon, 27.07.15 17:52, Keller, Jacob E (jacob.e.kel...@intel.com)
wrote:
Hello,
I am working with a network device that can create virtual function
devices. When I create a large (8) vfs for this device I get some
weird
On Mon, 27.07.15 21:08, Ben Gamari (b...@smart-cactus.org) wrote:
Lennart Poettering lenn...@poettering.net writes:
On Mon, 27.07.15 20:29, Ben Gamari (b...@smart-cactus.org) wrote:
Lennart Poettering lenn...@poettering.net writes:
On Fri, 17.07.15 12:23, Ben Gamari
On Thu, 16.07.15 12:40, Chris Murphy (li...@colorremedies.com) wrote:
Resurrection of related thread systemd and nested Btrfs subvolumes from
March:
http://lists.freedesktop.org/archives/systemd-devel/2015-March/029666.html
The question:
I understand the argument for subvolumes for
Lennart Poettering lenn...@poettering.net writes:
On Mon, 27.07.15 21:08, Ben Gamari (b...@smart-cactus.org) wrote:
Lennart Poettering lenn...@poettering.net writes:
On Mon, 27.07.15 20:29, Ben Gamari (b...@smart-cactus.org) wrote:
Ahh, of course. This is a Debian sid machine, so
On Mon, 27.07.15 15:37, Felipe Sateler (fsate...@debian.org) wrote:
On 27 July 2015 at 12:36, Lennart Poettering lenn...@poettering.net wrote:
On Mon, 27.07.15 15:19, Felipe Sateler (fsate...@debian.org) wrote:
On Mon, 27 Jul 2015 16:51:02 +0200, Lennart Poettering wrote:
Coming back
Lennart Poettering lenn...@poettering.net writes:
On Mon, 27.07.15 20:29, Ben Gamari (b...@smart-cactus.org) wrote:
Lennart Poettering lenn...@poettering.net writes:
On Fri, 17.07.15 12:23, Ben Gamari (b...@smart-cactus.org) wrote:
snip
Why might this be the case? Does nspawn
On Sun, 19.07.15 22:38, Paul Menzel (paulepan...@users.sourceforge.net) wrote:
1. The capability `SYS_ADMIN` has to be given(?) to the Docker
container.
--cap-add SYS_ADMIN
systemd should work OK now even if you don't pass the cap. That said,
this takes away the effect of things like
On Mon, Jul 27, 2015 at 08:48:08PM +0200, Lennart Poettering wrote:
On Tue, 21.07.15 03:27, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
[resending with the right systemd-devel address, sorry for that]
Here are some thoughts on offline updates resulting from testing
the new
On Mon, 27.07.15 19:37, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
OK, I think we're pretty much in agreement. I'd like to take the opportunity
to convert the wiki page to a man page. It would be easier to discuss
and track changes then. ?
I'd document systemd behaviour, apis and
On Tue, 14.07.15 18:34, Keller, Jacob E (jacob.e.kel...@intel.com) wrote:
Hello,
I created an nspawn container which is also running systemd. I can't
figure out why the systemd --user instances aren't started.
I'd like to manage some processes run as a specific user inside the
container.
On Mon, 2015-07-27 at 21:12 +0300, Andrei Borzenkov wrote:
В Mon, 27 Jul 2015 17:52:59 +
Keller, Jacob E jacob.e.kel...@intel.com пишет:
Hello,
I am working with a network device that can create virtual function
devices. When I create a large (8) vfs for this device I get some
On Mon, 27.07.15 20:29, Ben Gamari (b...@smart-cactus.org) wrote:
Lennart Poettering lenn...@poettering.net writes:
On Fri, 17.07.15 12:23, Ben Gamari (b...@smart-cactus.org) wrote:
snip
Why might this be the case? Does nspawn prevent the process from getting
a controlling tty?
On Wed, 15.07.15 16:24, Reindl Harald (h.rei...@thelounge.net) wrote:
why does systemd *randomly* try to create RuntimeDirectory
for ExecStartPost and so terminates a perfectly up and running service
because the file exists error?
Fedora 21 as well as Fedora 22
On Mon, 22.06.15 16:20, Johannes Ernst (johannes.er...@gmail.com) wrote:
I can import-tar, list-images, image-status, start, rename, and remove, but
sudo machinectl clone depot depot2
Could not clone image: Access denied
For completeness of the archives' sake: discussion about this has
Lennart Poettering lenn...@poettering.net writes:
On Fri, 17.07.15 12:23, Ben Gamari (b...@smart-cactus.org) wrote:
snip
Why might this be the case? Does nspawn prevent the process from getting
a controlling tty?
The pty setup code changed in nspawn evrsions, hence it is important
to say
On 27 July 2015 at 12:36, Lennart Poettering lenn...@poettering.net wrote:
On Mon, 27.07.15 15:19, Felipe Sateler (fsate...@debian.org) wrote:
On Mon, 27 Jul 2015 16:51:02 +0200, Lennart Poettering wrote:
Coming back to your original question, there are two options:
1) nfs-common becomes
On Tue, 21.07.15 03:27, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
[resending with the right systemd-devel address, sorry for that]
Here are some thoughts on offline updates resulting from testing
the new dnf fedup plugin developed by Will Woods
В Mon, 27 Jul 2015 18:29:57 +
Keller, Jacob E jacob.e.kel...@intel.com пишет:
On Mon, 2015-07-27 at 21:12 +0300, Andrei Borzenkov wrote:
В Mon, 27 Jul 2015 17:52:59 +
Keller, Jacob E jacob.e.kel...@intel.com пишет:
Hello,
I am working with a network device that can
On Mon, 2015-07-27 at 21:53 +0300, Andrei Borzenkov wrote:
В Mon, 27 Jul 2015 18:29:57 +
Keller, Jacob E jacob.e.kel...@intel.com пишет:
On Mon, 2015-07-27 at 21:12 +0300, Andrei Borzenkov wrote:
В Mon, 27 Jul 2015 17:52:59 +
Keller, Jacob E jacob.e.kel...@intel.com пишет:
On Mon, 2015-07-27 at 21:51 +0200, Lennart Poettering wrote:
On Tue, 14.07.15 18:34, Keller, Jacob E (jacob.e.kel...@intel.com)
wrote:
Hello,
I created an nspawn container which is also running systemd. I
can't
figure out why the systemd --user instances aren't started.
I'd
On Mon, 27.07.15 01:18, Christopher Cox (c...@endlessnow.com) wrote:
I suspect that somebody here knows why, but all mounts now fail... well
all but /.
Has anyone run across this before? What did I miss?
I accidentally messed up my boot mbr. and I did a rescue cd and chroot
in
order to
On Thu, 09.07.15 23:14, Vadim Berezniker (va...@berezniker.com) wrote:
If a service fails to start because a dependency fails but that dependency
successfully starts after an automatic restart, I would expect the failed
dependent to attempt to start as well now that its dependency is
happy.
On 27 July 2015 at 15:58, Lennart Poettering lenn...@poettering.net wrote:
On Mon, 27.07.15 15:37, Felipe Sateler (fsate...@debian.org) wrote:
On 27 July 2015 at 12:36, Lennart Poettering lenn...@poettering.net wrote:
On Mon, 27.07.15 15:19, Felipe Sateler (fsate...@debian.org) wrote:
On
c...@endlessnow.com composed on 2015-07-27 16:35 (UTC-0500):
A root is getting mounted and I figure it's the same but will double
check (away from system right now). Would some kind of root getting
mounted at startup and being different from root in /etc/fstab make some
sort of difference?
On Mon, 27.07.15 16:35, c...@endlessnow.com (c...@endlessnow.com) wrote:
On Mon, 27.07.15 01:18, Christopher Cox (c...@endlessnow.com) wrote:
I suspect that somebody here knows why, but all mounts now fail... well
all but /.
Has anyone run across this before? What did I miss?
I
On Tue, 07.07.15 13:04, Ernast Sevo (ers...@gmail.com) wrote:
Apologies that was mistakenly sent. The example service is below.
[Unit]
Before=local-fs.target
After=some service
DefaultDependencies=false
[Service]
Type=oneshot
ExecStart=/usr/bin/xxx
RemainAfterExit=yes
[Install]
On Wed, 15.07.15 17:30, Hoyer, Marko (ADITG/SW2) (mho...@de.adit-jv.com) wrote:
Systemd v211 added the running queue as deferred event source to the
event handling with priority IDLE. So dbus requests are preferred
over job execution. The reverse order effect is simply because the
run queue
On Tue, 23.06.15 13:30, Johannes Ernst (johannes.er...@gmail.com) wrote:
(Morale: in doubt, lean hard on your booleans)
1. Reboot host. (Arch running in VirtualBox on Mac)
2. host sysctl net.ipv4.ip_forward
net.ipv4.ip_forward = 1
This is the global option, it is related in non-obvious
I have a problem with what I thought would be a simple service unit:
# /etc/systemd/system/socat.service
[Service]
ExecStart=/usr/bin/socat UDP-RECV:4321 STDOUT
The expected outcome is that /usr/bin/socat UDP-RECV:4321 STDOUT is
started with its standard output connected to the
В Mon, 27 Jul 2015 19:05:37 +
Keller, Jacob E jacob.e.kel...@intel.com пишет:
On Mon, 2015-07-27 at 21:53 +0300, Andrei Borzenkov wrote:
В Mon, 27 Jul 2015 18:29:57 +
Keller, Jacob E jacob.e.kel...@intel.com пишет:
On Mon, 2015-07-27 at 21:12 +0300, Andrei Borzenkov wrote:
I suspect that somebody here knows why, but all mounts now fail... well all but
/.
Has anyone run across this before? What did I miss?
I accidentally messed up my boot mbr. and I did a rescue cd and chroot in order
to rerun grub2-mkconfig and do a grub2-install.
Now the system boots to a
On Mon, Jul 27, 2015 at 01:18:55AM -0500, Christopher Cox wrote:
I suspect that somebody here knows why, but all mounts now fail... well all
but /.
Has anyone run across this before? What did I miss?
I have seen this happen when I was using a kernel that was old and
didn't have
В Mon, 27 Jul 2015 08:15:45 +0300
Oleksii Shevchuk alx...@gmail.com пишет:
Andrei Borzenkov arvidj...@gmail.com writes:
So that it the problem. Does it happen if you use cryptsetup directly?
Yes, with cryptsetup behavior is the same.
I have cryptsetup (1.6.7) and lvm2 (2.02.116).
54 matches
Mail list logo
