From: Nacho de los RÃÂos Tormo <irios@proin.es>
To: sourcenav@sources.redhat.com
Subject: Weird permissions in SN5
Date: Wed, 04 Apr 2001 05:47:00 -0000 [thread overview]
Message-ID: <01040411582900.08677@irios> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
I have downloaded the Snav5 binary for Linux with great anticipation, and
have uncompressed the tar.gz file to /opt/snavigator .
I can start the program with /opt/snavigator/bin/snavigator only when root,
because files belong to user 1105 in group 1002, neither of which exist in my
system. This disallows me to execute Snav5 as a user. However, it DOES work
when called by root -- though this is useless to me, because my personal
directory resides in a network server, and it is unavailable for my station's
root user.
To chown everything to root.root is not enough, because the file permissions
are wrong for users not in the group, and access is disalowed.
Chowning to root.users looked as it might have worked, but then
/opt/snavigator/bin/snavigator originates an inmediate segmentation fault.
chmod everything to 755 also produces a segmentation fault.
Finally, I created a "snavigator" user 1105 and a "snavigator" group 1002 and
added my own user to the snavigator group. Time for segmentation fault again!
This is happening on SuSE Linux 7.0
What else can I do?
Thanks a lot,
Nacho de los RÃos Tormo
Procedimientos Integrados S.L.
Sevillanos, 67
28609 Sevilla la Nueva, Madrid
SPAIN
next reply other threads:[~2001-04-04 5:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-04 5:47 Nacho de los RÃos Tormo [this message]
2001-04-04 7:17 ` Marta Stojanovic
2001-04-05 22:39 ` Mo DeJong
2001-04-05 23:08 ` Mo DeJong
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=01040411582900.08677@irios \
--to=irios@proin.es \
--cc=sourcenav@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).