Re: Disappearing files, created from /etc/X11/Xclients

Please include freebsd-questions on any replies.

Laszlo Nagy wrote:


If os.getlogin() failed non-fatally and returned, say, and empty string, then you'd be creating a file called ".txt", if I read correctly. What does "ls -lsa /tmp/disklessips" show? Do you in fact have .txt and .history.txt files (which a simple ls won't show you).

There are no '.txt' and '.history.txt' files. :-(

Failing that, you'll just need to include some debugging. Open a file in /tmp to write stuff to, and print *all* the various variables you use to that file. (Or just print them to stdout if that will show up on the console). Then try as some other user and check that everything really does have the value you think it does.

Unfortunately, I cannot debug this way. The error is that no files are created by normal users, so I cannot use files for logging. Also there is no console because this is the /etcX11/Xclients script, e.g. it is executed by gdm after logging in to X window system through xdmpc. Well, I might setup an xml rpc server for logging, but hey, if I cannot write into a wicked file then I should not start with complex protocols and networking.

Humour me. Try opening a fixed filename in a location which you double-check is world-writeable. E.g. /tmp/FOO and print all your relevant variables there. If it works as gandalf, then delete that trace file and try as a non-working user.

If that fails, then try opening the file in the home directory of the user who you are testing as.

If that fails then you can try logging them with syslog.

If *that* fails then make your console world-writeable for a little while and print directly to that (/dev/console) (assuming there is a console which you can sit in front of).

One way or another you need to get debugging info to figure out what is not working.

I asked this on the FreeBSD questions list because I thought that there is some OS specific stuff that I don't know of.

There's no FreeBSD specific feature which makes file mysteriously vanish, that I'm aware of ;-)

Are you sure that if say the file() fails, that a window manager won't start anyway? You can test that by making the filename something clearly non-existent.

--Alex






_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Iptables and logging to the console
    ... How can I stop Iptables logging to the console? ... # Kernel sysctl configuration file for Red Hat Linux ... # Controls source route verification ...
    (Fedora)
  • Re: javaldx failed.
    ... mozilla start from default fails, ... error message. ... console in the icewm window but I resolved this for the console window ... get script ...
    (Debian-User)
  • Re: ptwilliams?
    ... > reset a secure channel password using RDP!! ... > logging into the console and getting a 'command completed successfully' ... > message, when I tried to open AD tools through Terminal Servcies, I get ...
    (microsoft.public.win2000.active_directory)
  • Re: debugging pppoe
    ... On Monday 11 June 2007 22:54, Michael P. Soulier wrote: ... I turned up the logging and I had to turn it down before it ... The default is ``set log local'' (i.e., ... Something else of possible interest is that ppp, can serve its console ...
    (freebsd-questions)
  • Re: Root Partition Fills Up Completely After a Few Hours
    ... > logged in to any text console, ... > log file, which gets rather full after a few hours. ... normally amount to just a few megabytes. ... There are a couple of ways to stop the logging to the console. ...
    (Debian-User)