From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: cups issue
Date: Mon, 04 Oct 2010 21:19:45 +0200 [thread overview]
Message-ID: <4CAA28D1.1010403@eukrea.com> (raw)
In-Reply-To: <AANLkTikO4fHqYzZJ5PDjmWV9Q3a9tBD_Y+rSs0iO6=5m@mail.gmail.com>
Hi Frans,
Le 04/10/2010 19:17, Frans Meulenbroeks a écrit :
> No idea who is the maintainer of cups, but I found the following issue:
>
> /etc/init.d/cups refers to ps ax but if you have busybox installed
> there are no ax options.
> As busybox has configurable columns it does not seem too good to fix
> cups to be able to handle both procps ps and busybox ps.
> Guess the preferred solution is to add a dependency to procps and get
> the real thing.
>
> However when wanting to make that change I bumped into the following:
>
> We have 6 cups recipes:
>
> cups_1.1.23.bb cups_1.2.12.bb cups_1.2.7.bb cups_1.3.8.bb
> cups_1.4.3.bb cups_1.4.4.bb
>
> The last three (!) of them have DP = "-1"
> Is there a point in add ing a recipe that has DP = "-1" for a
> prolonged time, then create a new version with DP = -1?
> (btw: and no version is pinned or so).
>
> Guess this recipe needs some love.
>
> (btw cups 1.4.4 solves a number of security issues; guess the best way
> forward is to test 1.4.4, then rm the old insecure stuff).
>
we are using 1.4.4 on armv5te and that works fine. I have a patch
concerning the ps ax init the init file which does :
if [ /bin/ps -ef /bin/busybox ]; then
pid=`ps w | awk '{if (match($5, ".*/cupsd$") || $5 == "cupsd") print
$1}'`
else
pid=`ps ax | awk '{if (match($5, ".*/cupsd$") || $5 == "cupsd")
print $1}'`
fi
so it can handle both case fine.
I can push it if this is an acceptable solution.
Eric
prev parent reply other threads:[~2010-10-04 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 17:17 cups issue Frans Meulenbroeks
2010-10-04 19:04 ` Henning Heinold
2010-10-04 19:19 ` Eric Bénard [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CAA28D1.1010403@eukrea.com \
--to=eric@eukrea.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox