On Fri, Oct 3, 2008 at 1:45 PM, Paul Johnson <pauljohn32@xxxxxxxxx> wrote: > I'm wondering if this is a widely experienced problem. I've found one > report about it in the Fedora bugzilla. > > I've noticed that the customized gdm PreSession/Default and > PostSession/Default scripts that I've been using for years in Fedora > 1-8 no longer run on a system that recently upgraded to Fedora 9. > There have been many changes in Fedora's gdm this time, no more > gdmsetup program and such, but as far as I can see in the > documentation, the scripts are supposed to run still, but they don't. > > This bug report says that the /etc/gdm/PostSession default is not executed > > https://bugzilla.redhat.com/show_bug.cgi?id=449675 > > THat's probably same as this one; > > https://bugzilla.redhat.com/show_bug.cgi?id=453483 > > It appears to me that neither PreSession nor PostSession is executed. > > You can see for yourself if you put something simple in PreSession/Default like > > echo "whatever" >> /tmp/checkingOnGDM > > It simply appears as if GDM is by passing the scripts altogether. > > It is important to me to know if we are just a few isolated people for > whom this does not work. I mean, does it work for nobody, but most > people don't try? Or does it work for some people? > > There are so many changes in the gdm used in F9 and the documentation > has not caught up with it, I think. > > Assuming gdm is broken, can you suggest an alternative way to run a > script every time users log in and log out? > > -- > Paul E. Johnson > Professor, Political Science > 1541 Lilac Lane, Room 504 > University of Kansas > > -- > fedora-list mailing list > fedora-list@xxxxxxxxxx > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > Hi Paul Johnson! If it was me I would be looking at the ownership, permissions, and SELinux context of the scripts. But that is me. I cannot answer your question about the scripts - my path to my Fedora is blocked by a nasty boot file compatability issue, I think. I have been experimenting with other OSs and just found out. Probably the best place to locate a script for a specific person logging in or out may well be in thier home directory as mentioned in the segment of the wikipedia artical on Bash which I found at http://en.wikipedia.org/wiki/Bash (remember, all processes are spawned in shells): --------------------------------------------------------------------- Startup scripts When Bash starts, it executes the commands in a variety of different scripts. When Bash is invoked as an interactive login shell, it first reads and executes commands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable. When a login shell exits, Bash reads and executes commands from the file ~/.bash_logout, if it exists. When an interactive shell that is not a login shell is started, Bash reads and executes commands from ~/.bashrc, if that file exists. This may be inhibited by using the --norc option. The --rcfile file option will force Bash to read and execute commands from file instead of ~/.bashrc. -------------------------------------------------------------------- If you need a more general solution you might add the script to /etc/rc.local. An introduction to this process is at http://www.linux.com/articles/114107 . Have Fun! Tod -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
