Le Friday 15 July 2005 17:24, Marty(Marty <[EMAIL PROTECTED]>)
disait:
Hi,
> I found that I couldn't log into X and /tmp permissions
> were set to 755 instead of 1777. Then I turned up this
> message in a list archive:
Haven't you unpacked a .deb using 'dpkg --e
Update: I just saw this on one of my other sarge systems,
so it looks like a systematic problem, and not a random
error on my part.
Marty wrote:
I found that I couldn't log into X and /tmp permissions
were set to 755 instead of 1777. Then I turned up this
message in a list archive:
I found that I couldn't log into X and /tmp permissions
were set to 755 instead of 1777. Then I turned up this
message in a list archive:
http://www.spinics.net/lists/xfree86/msg09446.html
Quote: "Thanks! I've no idea why the default permissions
weren't right."
ible.
I changed /tmp to rwxrwtrwt (IIRC) and it's working fine.
But I've been stung by this once before, over a year ago.
is there some way to check the packages to see which ones have some kind
of chmod execution in them?
Otherwise I'll have to do a reinstallation with a point-by-p
On Wed, Nov 19, 2003 at 09:42:32PM -0500, Tom Allison wrote:
> ls -l /:
> drwxr-xr-x root root tmp
>
> This is the problem.
>
> It's an extremely severe bug.
Not really, it's easily reversible.
> Settings that might have influenced this:
> Users cannot view each others $HOME directory
> '
OK, I finally figured out what the cause, possibly, of my problem I've
been struggling with over several postings/days here.
The problem is that I have been unable to login via xdm/XFree as a
regular user. Root is OK.
The answer/clue is in the ~/.xsession-errors file.
It's also related to a i
No problem here...
I installed from the potato boot flops.
Regards,
Onno
At 03:10 AM 11/19/99 +0100, J Horacio MG wrote:
Hi,
all of a sudden I realized the /tmp permissions had changed to:
2 drwxr-xr-x 5 root root 2048 Nov 19 02:57 tmp/
so, I changed it back to sticky with
Hi,
all of a sudden I realized the /tmp permissions had changed to:
2 drwxr-xr-x 5 root root 2048 Nov 19 02:57 tmp/
so, I changed it back to sticky with:
# chmod 777 /tmp
# chmod a+t /tmp
Now, it seems alright, but I'm not sure about the rest (most of all
/var). Could a
Traditionally, /tmp should probably be chmod 1777, owned by root.root. (The
1 makes it impossible to delete other user's files..)
On Mon, Sep 06, 1999 at 01:58:01PM -0500, Robert Rati wrote:
> I was running xdm and kde just happily and I decided to kick up to xdm
> windows. No problem. Well, for
On Mon, Sep 06, 1999 at 01:58:01PM -0500, Robert Rati wrote:
> I was running xdm and kde just happily and I decided to kick up to xdm
> windows. No problem. Well, for some reason, KDE now complains that it
> needs write permissions to the /tmp dir. What are the permissions and
> ownership suppos
On Mon, 6 Sep 1999, Robert Rati wrote:
> I was running xdm and kde just happily and I decided to kick up to xdm
> windows. No problem. Well, for some reason, KDE now complains that it
> needs write permissions to the /tmp dir. What are the permissions and
> ownership supposed to be for /tmp and
I was running xdm and kde just happily and I decided to kick up to xdm
windows. No problem. Well, for some reason, KDE now complains that it
needs write permissions to the /tmp dir. What are the permissions and
ownership supposed to be for /tmp and does anyone know HOW the permissions
could've g
>> "Andrew" == Andrew Martin Adrian Cater <[EMAIL PROTECTED]> writes:
Andrew> On ED /tmp has permissions of 755 so nothing can write temp files.
Either that, or you untar'ed some archive as root into /tmp that had
the . directory in it.
One should always untar in a subdirectory of /tmp.
Andrew
Just installed Essential Debian at work as an experiment: fairly pleased
with a minimal Debian on one disk (we already have Debian machines
running Slink) BUT
The permissions on /tmp may be wrong.
As root/super user all is OK. Can't use vi or man as a normal user
because there is no permission t
On Mon, Sep 14, 1998 at 04:57:08PM -0600, Phil Humpherys wrote:
>
> Nuno Carvalho <[EMAIL PROTECTED]> writes:
>
> > It's a "good policy" for /tmp directory to have 777
> > permissions !? With such permissions any user could write on
> > that directory until even > there's no more space on dev
Nuno Carvalho <[EMAIL PROTECTED]> writes:
> It's a "good policy" for /tmp directory to have 777
> permissions !? With such permissions any user could write on
> that directory until even > there's no more space on device,
> rigth !?
Yup, though if he's not the root user, he won't be able to
Hi,
Thanks for all who reply to me explaining that question.
At the moment, i'd a better idea. :)
Best regards,
Nuno Carvalho
On Sun, 13 Sep 1998, Nuno Carvalho wrote:
: Hi,
:
: I'de some questions about /tmp directory:
:
: My /tmp directory permissions are:
:
: rwxrwxrwt 2 root root 1024 Sep 13 14:17 tmp
:
: ... meanwhile chmod manual says that "t" permission is to: save program
: tex
On Sun, 13 Sep 1998, Nuno Carvalho wrote:
>
> It's a "good policy" for /tmp directory to have 777 permissions !?
> With such permissions any user could write on that directory until even
> there's no more space on device, rigth !?
>
That's exactly what it is for (not writing till the disk is f
Hi,
I'de some questions about /tmp directory:
My /tmp directory permissions are:
rwxrwxrwt 2 root root 1024 Sep 13 14:17 tmp
... meanwhile chmod manual says that "t" permission is to: save program
text on swap device !
What this means !? /tmp directory isn't on any swap
Not so good. Seems cron died on my production machine a few days ago,
not mentioned in the logs. And just recently /tmp went unworld-writable,
which meant cgi scripts didn't work. :-( Anyone got a fix for this?
Happens quite often on my personal machine too.
hamish
--
TO UNSUBSCRIBE FROM THIS
21 matches
Mail list logo
