Description of problem: ps(1) mentions "unit" field, but it doesn't seem to work. $ ps -eo pid,user,args,unit error: unknown user-defined format specifier "unit" Version-Release number of selected component (if applicable): $ rpm -qf /usr/bin/ps procps-ng-3.3.8-8.fc19.x86_64
Hello Zbigniew. The feature is pretty recent and unfortunately I forgot to enable the systemd support in the F19 zero day update. As introducing new features in stable Fedora releases kind of breaks our policy, it's probably too late for introducing this in Fedora 19, but you can install the latest F20 package (procps-ng-3.3.8-16.fc20) where the systemd support is enabled. Please, let me know if you're ok with this approach. Thanks in advance. Regards, Jaromir.
(In reply to Jaromír Cápík from comment #1) > but you can install the latest F20 package > (procps-ng-3.3.8-16.fc20) where the systemd support is enabled. Sorry, typo in the previous comment ... procps-ng-3.3.8-13.fc20
Hi Jaromír, I can install procps from rawhide without problem, and I can confirm that it works fine. Regarding F19, I think that since this feature has been advertised (I read about on the net somewhere, that's why I tried to use it), and it's documented, it'll be confusing for people. Personally I'd treat this a bug fixable in released version, since it's unlikely to break things.
(In reply to Zbigniew Jędrzejewski-Szmek from comment #3) > I can install procps from rawhide without problem, and I can confirm that it > works fine. Good. > Regarding F19, I think that since this feature has been advertised (I read > about on the net somewhere, that's why I tried to use it), Could you please find the article? > and it's documented, it'll be confusing for people. All optional features are documented. Maybe we should state, they're optional, somewhere in the manual. That could help users to avoid confusions. > Personally I'd treat this a bug > fixable in released version, since it's unlikely to break things. Introducing a new library is always risky. Especially when we're talking about critical path components. Please, let me know. Thank you, Jaromir.
(In reply to Jaromír Cápík from comment #4) > (In reply to Zbigniew Jędrzejewski-Szmek from comment #3) > > I can install procps from rawhide without problem, and I can confirm that it > > works fine. > > Good. > > > > Regarding F19, I think that since this feature has been advertised (I read > > about on the net somewhere, that's why I tried to use it), > > Could you please find the article? Sorry, it's been a while, I totally forgot where I saw it. Could even have been on IRC. > > and it's documented, it'll be confusing for people. > > All optional features are documented. Maybe we should state, they're > optional, somewhere in the manual. That could help users to avoid confusions. > > > Personally I'd treat this a bug > > fixable in released version, since it's unlikely to break things. > > Introducing a new library is always risky. Especially when we're talking > about critical path components. > > Please, let me know. Sorry, can't provide any useful information.
Hello Zbigniew. I can't find any references to such advertisement and even my colleagues are unsure. Hopefully you won't feel offended by my decision to keep the feature disabled in F19. Thanks for understanding. Regards, Jaromir.
*** Bug 1004465 has been marked as a duplicate of this bug. ***