Sebastian Tennant <[EMAIL PROTECTED]> wrote:
> OK, but mandb _is_ a member of the root group, so shouldn't it be able
> to write files in /tmp with the permissions as they stand?
No, you'd have to make it setuid to root, or setgid to the root
group. The user/group associations in /etc/passwd and
[EMAIL PROTECTED] (Paul Jarc) wrote:
> Sebastian Tennant <[EMAIL PROTECTED]> wrote:
>> I have a 3-line script; foo:
>
> The setuid bit works only for binaries, not scripts. This is a
> limitation of the kernel, necessary for security.
Ah. I read the chmod manpage and some stuff in the find Info
Arjen Meek wrote:
> Hello,
>
> I'm having a problem in bash 3.1 that I'm pretty sure is a bug. As
> indicated in the subject, the HISTCMD variable always returns 1 when
> used in PROMPT_COMMAND , rather than the actual number of the current
> line in the history.
It's not a bug. Bash-3.1 return
Mike Frysinger wrote:
> On Saturday 24 December 2005 13:27, Chet Ramey wrote:
>> Mike Frysinger wrote:
>>> On Thu, Dec 22, 2005 at 09:24:06AM -0500, Chet Ramey wrote:
Bash-Release: 3.1
Patch-ID: bash31-001
Bug-Description:
There are parsing problems with compound assig
Sebastian Tennant <[EMAIL PROTECTED]> wrote:
> I have a 3-line script; foo:
The setuid bit works only for binaries, not scripts. This is a
limitation of the kernel, necessary for security.
> A cron.daily script handles mandb. I elected to install it with the
> set-user-id bit set, as you can se
Hi all,
If it's a festive time of year where you are then I hope you're
enjoying it.
First of all, apologies if this is not the correct list for this
query. Perhaps you could suggest where else I should go.
I have a 3-line script; foo:
#!/bin/bash
id -u # EUID
id -u -r # `re
Interesting, here in big5 land I notice set -x will encode into octal
its output unless the item has certian printing non alphanumerics in
it I suppose. Anyways, there should be a way to tell set -x that one
doesn't want the $'' help, and would just like the raw chars. Also a
way to have set -x pri
