John, Okay, I could not find any information about an audio environment variable, save for Solaris. I also tried changing the permissions on every audio device on my system, which made my aumix errors go away but did not produce sound from my application to the speakers when I logged in as a non-root user. However, when I log in as root and launch my application as root, my application plays as designed. However, I was really hoping not to have to run my application as root... Take care, Darwin --- CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive work product privilege by the transmission of this message. -----Original Message----- From: pam-list-admin@redhat.com [mailto:pam-list-admin@redhat.com] On Behalf Of Matthews, John Sent: Friday, March 29, 2002 8:31 AM To: 'pam-list@redhat.com' Subject: RE: Remote Console Login What did you modify in PAM to allow you to access the display? I've done a lot of work on remote displays and I never knew about modifying PAM for it to work. I've simply redirected my DISPLAY env variable and run "xhost +" on the target machine. As far as audio goes, I believe there is an X environment variable that might allow you redirect the sound too, if that's what your after. I saw it somewhere, it might be something like "XSPEAKER" but I'm not really sure. If you don't want to redirect the audio, but are just having problems opening it, look at the /dev/dsp or whatever devices your sound card is and examine the permissions and owners. I've noticed that if I try to log into a remote machine that somebody is running an GNOME or KDE session on that I can't work with the audio device. It appears like the graphical clients lock the audio device for their own use. I haven't learned of a clean solution to this yet. I generally just take ownership of the device myself, or set permissions for everyone to write. There's probably a better solution than what I'm doing. -----Original Message----- From: Darwin Airola [mailto:Darwin@MusePlay.com] Sent: Thursday, March 28, 2002 2:52 PM To: pam-list@redhat.com Subject: RE: Remote Console Login Hello, again! I just read the message that I sent out to the group and I think that it is unclear what I am trying to do. Basically, what I want to do is to be able to startup (via a remote login) a multimedia X11 application that I wrote. I want the application to run on the machine that I am remotely logged into and to be able to access the audio of the machine that I am remotely logged into. I seem to have the system setup so that my application can access the display of the machine that I am remotely logged into, but I cannot figure out how to modify the PAM configuration so that my application can access the audio device of the machine that I am remotely logged into. To be able to access the display of the machine that I am remotely logged into, I did have to make changes to the PAM configuration before it would allow me to start up the X server on that machine via my remote login to that machine... Thus, I am quite certain that I need to make some other changes to my PAM configuration before I will be able to access the audio device on that machine, especially since I can access the audio device if I log into the machine via a local console login... Take care, Darwin -----Original Message----- From: pam-list-admin@redhat.com [mailto:pam-list-admin@redhat.com] On Behalf Of Darwin Airola Sent: Thursday, March 28, 2002 1:40 PM To: pam-list@redhat.com Subject: Remote Console Login Hello! I am having some extreme difficulty setting up RedHat V7.2 to accept a remote console login that behaves identically to a local console login. If I login to my machine remotely (via ssh) and then run startx on :0.0 (the local display), I cannot set run aumix (it returns with errors stating that it cannot access the audio device). HOWEVER, if I login locally and then run startx on :0.0 and THEN logout, I can immediately login remotely (via the same account that I just performed the local login with), run startx on :0.0 and access aumix of the machine that I am logged into. However, after some period of time, aumix (and the audio device) become inaccessible to me. Can one of you smart people please tell me how I can setup RedHat so that I can remotely login to a machine and obtain a remote console login that is identical to the standard RedHat local console login? Any assistance with this matter would be GREATLY appreciated! Take care, Darwin --- CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive work product privilege by the transmission of this message. _______________________________________________ Pam-list@redhat.com https://listman.redhat.com/mailman/listinfo/pam-list _______________________________________________ Pam-list@redhat.com https://listman.redhat.com/mailman/listinfo/pam-list
