[Solved] Close virtual X session?

I can start a virtual X session with
startx -- :1 &
Then I'm able to switch to tty8. When I'm done I want to close these X session on tty8.
Is there any console command to do this?
Last edited by arcc (2011-12-04 22:37:28)

I'm running X on tty4 and it's the only process listed to run there:
[karol@black ~]$ pidof X
18850
[karol@black ~]$ pgrep -t tty4
18850
Have you tried killing it with pkill?
Last edited by karol (2011-12-04 22:23:20)

Similar Messages

What is the proper way to close all open sessions of a NI PXI-4110 for a given Device alias?

I've found that, when programming the NI PXI-4110 that, if a the VI "niDCPower Initialize With Channels VI" (NI-DCPower pallette) is called with a device
alias that all ready has one or more sessions open (due to an abort or other programming error) a device reference results from the reference out that has a (*) where "*" is post-fixed to the device reference where and is an integer starting that increments with each initialize call. In my clean up, I would like to close all open sessions. For example, let's said the device alias is "NIPower_1" in NI Max, and there are 5 open sessions; NIPower_1, NIPower_1 (1), NIPower_1 (2), NIPower_1 (3), and NIPower_1 (4). A simple initialize or reset (using niDCPower Initialize With Channels VI, or, niDCPower Initialize With Channels VI, etc.) What is the proper way to close all open sessions?
Thanks in advance. Been struggleing with this for days!

When you Initialize a session to a device that already has a session open, NI-DCPower closes the previous session and returns a new one. You can verify this very easily: try to use the first session after the second session was opened.
Unfortunately, there is a small leak and that is what you encountered: the previous session remains registered with LabVIEW, since we unregister inside the Close VI and this was never called. So the name of the session still shows in the control like you noted: NIPower_1, NIPower_1 (1), NIPower_1 (2), NIPower_1 (3), and NIPower_1 (4), etc.
There may be a way to iterate over the registered sessions, but I couldn't find it. However, you can unregister them by calling "IVI Delete Session". Look for it inside "niDCPower Close.vi". If you don't have the list of open sessions, but you have the device name, then you can just append (1), (2) and so forth and call "IVI Delete Session" in a loop. There's no problem calling it on sessions that were never added.
However - I consider all this a hack. What you should do is write code that does not leak sessions. Anything you open, you should close. If you find yourself in a situation where there are a lot of leaked sessions during development, relaunching LabVIEW will clear it out. If relaunching LabVIEW is too much of an annoyance, then write a VI that does what I described above and run it when needed. You can even make it "smarter" by getting the names of all the NI-DCPower devices in your system using the System Configuration or niModInst APIs.
Hope this helps.
Marcos Kirsch
Principal Software Engineer
Core Modular Instruments Software
National Instruments

How do I close a generation session in C#

Hello,
   Please see the code below, how do I close the generation session after I have completed the io operations?
static void Main(string[] args)
{ /* start of main */
string card_name = "PXI-6552";
bool id_query_status = false;
bool reset_instrument_status = false;
string output_channels = "0,1,2,3,10,11,12";
string input_channels = "13";
uint misc_counter=0;
uint write_data=0x00000000;
uint mask_value=0XFFFFFFFF;
niHSDIO sig_gen = niHSDIO.InitGenerationSession(card_name,id_query_status,reset_instrument_status,"");
/* create a generation session to the Digital IO card */
sig_gen.AssignStaticChannels(output_channels);
sig_gen.ConfigureDataVoltageLogicFamily(output_channels,InstrumentDriverInterop.Ivi.niHSDIOConstants._33vLogic);
misc_counter = 0;
while(misc_counter <= 10000)
sig_gen.WriteStaticU32(0x00000000,mask_value);
sig_gen.WriteStaticU32(0xFFFFFFFF,mask_value);
Console.Write(misc_counter+"\n");
misc_counter++;
} /* end of main */
How do I close the generation session?
Regards,
Kaspar
Regards,
Kaspar

Kaspar,
I have some more information that might help explain how (and why) the Dispose() method works. If you look at the definition of Dispose() you see that it calls a private method, Dispose(bool). This wrapper function contains a direct call to the Close() function imported from niHSDIO.dll. Thus you are calling the Close() method that you are probably used to seeing in the C version it has just been updated to work in C#. Hope this is helpful!
public void Dispose(){
this.Dispose(true);
System.GC.SuppressFinalize(this);
private void Dispose(bool disposing){
  if ((this._disposed == false)){
    PInvoke.close(this._handle);
    this._handle = System.IntPtr.Zero;
this._disposed = true;
John B.
Applications Engineer
National Instruments

Can't close my icloud session

I can't close my icloud session on my friends Imac.
Please help me, we cannot do any thing else, everything is so so slow.
T
Many thanks,

Not sure what you mean by 'iCloud session' - iCloud runs in the background and you don't start and stop it. Are you accessing it in a browser such as Safari? If you can't exit it there then press commane-option-escape and choose the browser in the list, then force quit it.

RDS 2012-PUBLISING REMOTEAPPS WITH VIRTUAL DESKTOP SESSION

Hello, I deployed a RDS 2012 VIRTUAL DESKTOP SESSION FARM.
Is it possible publish a REMOTEAPPS with Virtual Desktop Session?, I only find information with Remote Desktop Session
Thanks
Regards

Hi,
Seems this is not the possible scenario for deployment, we need to have Session based deployment as both virtual desktop session and session based deployment differs from other.
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Adobe freezing virtual desktop session

We have classrooms with Windows 7 Virtual desktops running on Xendesktop. When a student has multople adobe documents opan and attempts a search, it freezes the sessoin. I then have to forcably reboot virtual desktop in order to release the session.

Hi,
Seems this is not the possible scenario for deployment, we need to have Session based deployment as both virtual desktop session and session based deployment differs from other.
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

How to close a HTTP session when a user closes the window

Hi,
I am having problems when closing the browser of a BW web report. After I closed the browser by going File->close, I ran SM04 and found out the Plugin HTTP session hangs at the server side.
How can we terminate the Plugin HTTP session at the server side when user closes the internet browser?
I did implement a logoff function at my web template and this was implimented on the Menu page, if user clicks on the logoff, the Plugin HTTP session is terminated at server side correctly.
If user navigates to the other pages from the main page... then the logoff function was not implimented in the other pages. So many of the users are closing the windows directly. Eevn if we impliment logoff in all the subpages, As you know, 50% of time user will close the report by closing the internet browser instead of clicking the logoff. That leaves lots of hanging Plugin HTTP sessions at our server side.
Regards,
Tony

Hi,
And also take a look on the Genral property of the web template. We solved this problem by changing only this property (no extra things).
<b>Property: Value</b>
Automatic Session Management: Active
With rgds,
Anil Kumar Sharma .P
Message was edited by: Anil Kumar Sharma

Why do I get an error message that tells me I need to close the current session of Firefox. It is open somewhere and I must restart my computer to get past this. Why?

I cannot open Firefox on my system as a message opens that tells me I must close the session that is currently running. However, I have not opened it and it doesn't show anywhere on my computer that it is open. The error message tells me that I must restart my computer which I have to do to get past this point. Then it works fine after that. I have been using Firefox for about 5 months and it has happened about 6 times now. A bit frustrating I must say. Thank you for your assistance on this matter.

Open Task Manager and click on the Processes tab. Scroll down to "Firefox.exe" , click on that line and click on "End Process" button.

If I close a session on Firefox and then try to reopen it, I get a screen that says "you must close your current session because Firefox is already running".

The power went out and when it came back on, my computer seemed fine. I was able to access the internet through Firefox as usual. However, if I closed my session and tried to reopen it, it would say that there was already a session open and that I would have to close it before trying again. I would have to go to the task manager and find Firefox in the list of processes and end the process in order to get back to the internet. I have tried restarting my computer twice. What could be the problem?

Try to wait a bit longer before reopening Firefox to give Firefox more time to close completely.<br />
You can also try to use Firefox/File > Exit to close Firefox.
See "Hang at exit":
*http://kb.mozillazine.org/Firefox_hangs
*https://support.mozilla.com/kb/Firefox+hangs
See also:
* http://kb.mozillazine.org/Profile_in_use
* https://support.mozilla.com/kb/Firefox+is+already+running+but+is+not+responding

(Solved)Xorg virtual res.change

How do i get the virtual resolution change by ctrl+alt+(numpad)+ to work? (not real change as with xrandr, this is more like zooming)
This is the first install i have experienced where this is not working with the settings i have used for many years.
This is what i use
Section "Screen"
Identifier "Screen1"
Device "NVIDIA"
Monitor "SyncM"
DefaultDepth 24
Subsection "Display"
Depth 24
Modes "1280x960" "1024x768" "800x600"
EndSubsection
EndSection
Another strange thing is that my screen goes about 20 pixels off screen to the left with the above, but if i comment out just the Modes line it becomes normal and keeps within the borders, but that Modes line needs normally to be there to have different virual resolutions.
Last edited by steelneck (2011-08-27 22:48:24)

Solved!
Now i can zoom by ctrl-alt-keypad+
This had something to do with the nouveau Nvidia kernel driver. I changed the driver in the xorg.conf to the old "nv" and blacklisted nouveau in the /etc/modprobe.d/modprobe.conf, since xorg refused to use nv as long as the nouveau was loaded in the kernel. So this actually looks like kernel driver bug.
Last edited by steelneck (2011-08-27 22:49:22)

[SOLVED] Cannot start X session from login

I don't know what exactly is going on. I'm using the nvidia package from the repo and kernel 2.6.32.6-1. I'm having trouble starting a second X session using:
startx -- :1
but this works fine
su -
startx -- :1
This is my xorg.conf
# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings: version 1.0 (buildmeister@builder75) Tue Dec 8 21:07:34 PST 2009
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
Option "Xinerama" "0"
EndSection
Section "ServerFlags"
Option "DontZap" "false"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "dbe"
Load "glx"
Load "extmod"
Load "dri"
Disable "dri2"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "ViewSonic VA1930wm-3"
DisplaySize 370 300
HorizSync 30.0 - 82.0
VertRefresh 50.0 - 75.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 6200 A-LE"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "AddARGBGLXVisuals" "True"
Option "TwinView" "0"
Option "TwinViewXineramaInfoOrder" "CRT-0"
Option "metamodes" "nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Extensions"
Option "Composite" "Enable"
EndSection
And the xorg error when I'm not root
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
X.Org X Server 1.7.3.902 (1.7.4 RC 2)
Release Date: 2009-12-26
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32-ARCH i686
Current Operating System: Linux nonsense 2.6.32-ARCH #1 SMP PREEMPT Mon Jan 25 20:06:48 UTC 2010 i686
Kernel command line: root=/dev/mapper/group-root vga=773 resume=/dev/mapper/group-swap ro
Build Date: 26 December 2009 11:37:45AM
Current version of pixman: 0.16.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Sat Jan 30 21:42:17 2010
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "X.org Configured"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Device0"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(**) Option "DontZap" "false"
(**) Option "Xinerama" "0"
(==) Automatically adding devices
(==) Automatically enabling devices
(**) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1,
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1
(**) ModulePath set to "/usr/lib/xorg/modules"
(**) Extension "Composite" is enabled
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Mouse0
(WW) Disabling Keyboard0
(II) Loader magic: 0x81e4c60
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 6.0
X.Org XInput driver : 7.0
X.Org Server Extension : 2.0
(--) using VT number 8
(--) PCI:*(0:1:0:0) 10de:0222:3842:a295 nVidia Corporation NV44 [GeForce 6200 A-LE] rev 161, Mem @ 0xbf000000/16777216, 0xe0000000/268435456, 0xbe000000/16777216, BIOS @ 0x????????/131072
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) "dri2" will not be loaded unless you've specified it to be loaded elsewhere.
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri2" will be loaded even though the default is to disable it.
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.7.3.902, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 190.53 Tue Dec 8 20:47:42 PST 2009
(II) Loading extension GLX
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.7.3.902, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.7.3.902, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
dlopen: /usr/lib/xorg/modules/drivers/nvidia_drv.so: undefined symbol: dixLookupResource
(EE) Failed to load /usr/lib/xorg/modules/drivers/nvidia_drv.so
(II) UnloadModule: "nvidia"
(EE) Failed to load module "nvidia" (loader failed, 7)
(EE) No drivers available.
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.1.log" for additional information.
Last edited by silentcontender (2010-02-02 01:13:54)

You are right about the first X session starting normally. I'm using the same user for both session and nvidia loads fine the first time. The log for the first X session:
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
X.Org X Server 1.7.3.902 (1.7.4 RC 2)
Release Date: 2009-12-26
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.32-ARCH i686
Current Operating System: Linux nonsense 2.6.32-ARCH #1 SMP PREEMPT Mon Jan 25 20:06:48 UTC 2010 i686
Kernel command line: root=/dev/mapper/group-root vga=795 resume=/dev/mapper/group-swap ro
Build Date: 26 December 2009 11:37:45AM
Current version of pixman: 0.16.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Jan 31 22:11:14 2010
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Layout0"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Device0"
(**) |-->Input Device "Keyboard0"
(**) |-->Input Device "Mouse0"
(==) Automatically adding devices
(==) Automatically enabling devices
(==) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1
(==) ModulePath set to "/usr/lib/xorg/modules"
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Keyboard0
(WW) Disabling Mouse0
(II) Loader magic: 0x81e4c60
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 6.0
X.Org XInput driver : 7.0
X.Org Server Extension : 2.0
(++) using VT number 7
(--) PCI:*(0:1:0:0) 10de:0222:3842:a295 nVidia Corporation NV44 [GeForce 6200 A-LE] rev 161, Mem @ 0xbf000000/16777216, 0xe0000000/268435456, 0xbe000000/16777216, BIOS @ 0x????????/131072
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.7.3.902, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.7.3.902, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions/libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module 190.53 Tue Dec 8 20:47:42 PST 2009
(II) Loading extension GLX
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.7.3.902, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.7.3.902, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) NVIDIA dlloader X Driver 190.53 Tue Dec 8 19:16:02 PST 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is: PCI 01@00:00:0
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.7.3.902, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib/xorg/modules/libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
compiled for 1.7.3.902, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) Jan 31 22:11:15 NVIDIA(0): Enabling RENDER acceleration
(II) Jan 31 22:11:15 NVIDIA(0): Support for GLX with the Damage and Composite X extensions is
(II) Jan 31 22:11:15 NVIDIA(0): enabled.
(II) Jan 31 22:11:15 NVIDIA(0): NVIDIA GPU GeForce 6200 A-LE (NV44) at PCI:1:0:0 (GPU-0)
(--) Jan 31 22:11:15 NVIDIA(0): Memory: 262144 kBytes
(--) Jan 31 22:11:15 NVIDIA(0): VideoBIOS: 05.44.a2.10.01
(II) Jan 31 22:11:15 NVIDIA(0): Detected AGP rate: 8X
(--) Jan 31 22:11:15 NVIDIA(0): Interlaced video modes are supported on this GPU
(--) Jan 31 22:11:15 NVIDIA(0): Connected display device(s) on GeForce 6200 A-LE at
(--) Jan 31 22:11:15 NVIDIA(0): PCI:1:0:0:
(--) Jan 31 22:11:15 NVIDIA(0): ViewSonic VA1930wm-3 (CRT-0)
(--) Jan 31 22:11:15 NVIDIA(0): ViewSonic VA1930wm-3 (CRT-0): 400.0 MHz maximum pixel clock
(II) Jan 31 22:11:15 NVIDIA(0): Assigned Display Device: CRT-0
(==) Jan 31 22:11:15 NVIDIA(0):
(==) Jan 31 22:11:15 NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
(==) Jan 31 22:11:15 NVIDIA(0): will be used as the requested mode.
(==) Jan 31 22:11:15 NVIDIA(0):
(II) Jan 31 22:11:15 NVIDIA(0): Validated modes:
(II) Jan 31 22:11:15 NVIDIA(0): "nvidia-auto-select"
(II) Jan 31 22:11:15 NVIDIA(0): Virtual screen size determined to be 1440 x 900
(--) Jan 31 22:11:15 NVIDIA(0): DPI set to (89, 87); computed from "UseEdidDpi" X config
(--) Jan 31 22:11:15 NVIDIA(0): option
(==) Jan 31 22:11:15 NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) Jan 31 22:11:15 NVIDIA(0): Initialized AGP GART.
(II) Jan 31 22:11:15 NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
(II) Jan 31 22:11:15 NVIDIA(0): may not be running or the "AcpidSocketPath" X
(II) Jan 31 22:11:15 NVIDIA(0): configuration option may not be set correctly. When the
(II) Jan 31 22:11:15 NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
(II) Jan 31 22:11:15 NVIDIA(0): try to use it to receive ACPI event notifications. For
(II) Jan 31 22:11:15 NVIDIA(0): details, please see the "ConnectToAcpid" and
(II) Jan 31 22:11:15 NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
(II) Jan 31 22:11:15 NVIDIA(0): Config Options in the README.
(II) Jan 31 22:11:15 NVIDIA(0): Setting mode "nvidia-auto-select"
(II) Loading extension NV-GLX
(II) Jan 31 22:11:15 NVIDIA(0): Initialized OpenGL Acceleration
(==) NVIDIA(0): Disabling shared memory pixmaps
(II) Jan 31 22:11:15 NVIDIA(0): Initialized X Rendering Acceleration
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(II) Loading extension XINERAMA
(==) RandR enabled
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing extension GLX
(II) config/hal: Adding input device Macintosh mouse button emulation
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.7.3, module version = 2.3.2
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 7.0
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found relative axes
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
(**) Macintosh mouse button emulation: (accel) acceleration profile 0
(II) Macintosh mouse button emulation: initialized for relative axes.
(II) config/hal: Adding input device Logitech USB Receiver
(**) Logitech USB Receiver: always reports core events
(**) Logitech USB Receiver: Device: "/dev/input/event5"
(II) Logitech USB Receiver: Found 12 mouse buttons
(II) Logitech USB Receiver: Found scroll wheel(s)
(II) Logitech USB Receiver: Found relative axes
(II) Logitech USB Receiver: Found x and y relative axes
(II) Logitech USB Receiver: Found absolute axes
(II) Logitech USB Receiver: Found keys
(II) Logitech USB Receiver: Configuring as mouse
(II) Logitech USB Receiver: Configuring as keyboard
(**) Logitech USB Receiver: YAxisMapping: buttons 4 and 5
(**) Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
(**) Logitech USB Receiver: (accel) acceleration profile 0
(II) Logitech USB Receiver: initialized for relative axes.
(WW) Logitech USB Receiver: ignoring absolute axes.
(II) config/hal: Adding input device Logitech USB Receiver
(**) Logitech USB Receiver: always reports core events
(**) Logitech USB Receiver: Device: "/dev/input/event4"
(II) Logitech USB Receiver: Found keys
(II) Logitech USB Receiver: Configuring as keyboard
(II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event2"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event3"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) Jan 31 22:14:10 NVIDIA(0): Setting mode "nvidia-auto-select"
(II) Jan 31 22:14:10 NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
(II) Jan 31 22:14:10 NVIDIA(0): may not be running or the "AcpidSocketPath" X
(II) Jan 31 22:14:10 NVIDIA(0): configuration option may not be set correctly. When the
(II) Jan 31 22:14:10 NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
(II) Jan 31 22:14:10 NVIDIA(0): try to use it to receive ACPI event notifications. For
(II) Jan 31 22:14:10 NVIDIA(0): details, please see the "ConnectToAcpid" and
(II) Jan 31 22:14:10 NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
(II) Jan 31 22:14:10 NVIDIA(0): Config Options in the README.
(II) Macintosh mouse button emulation: Device reopened after 1 attempts.
(II) Logitech USB Receiver: Device reopened after 1 attempts.
(II) Logitech USB Receiver: Device reopened after 1 attempts.
(II) Power Button: Device reopened after 1 attempts.
(II) Power Button: Device reopened after 1 attempts.
(II) Jan 31 22:14:22 NVIDIA(0): Setting mode "nvidia-auto-select"
(II) Jan 31 22:14:22 NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
(II) Jan 31 22:14:22 NVIDIA(0): may not be running or the "AcpidSocketPath" X
(II) Jan 31 22:14:22 NVIDIA(0): configuration option may not be set correctly. When the
(II) Jan 31 22:14:22 NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
(II) Jan 31 22:14:22 NVIDIA(0): try to use it to receive ACPI event notifications. For
(II) Jan 31 22:14:22 NVIDIA(0): details, please see the "ConnectToAcpid" and
(II) Jan 31 22:14:22 NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
(II) Jan 31 22:14:22 NVIDIA(0): Config Options in the README.
(II) Macintosh mouse button emulation: Device reopened after 1 attempts.
(II) Logitech USB Receiver: Device reopened after 1 attempts.
(II) Logitech USB Receiver: Device reopened after 1 attempts.
(II) Power Button: Device reopened after 1 attempts.
(II) Power Button: Device reopened after 1 attempts.
(II) Jan 31 22:16:23 NVIDIA(0): Setting mode "nvidia-auto-select"
(II) Jan 31 22:16:23 NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
(II) Jan 31 22:16:23 NVIDIA(0): may not be running or the "AcpidSocketPath" X
(II) Jan 31 22:16:23 NVIDIA(0): configuration option may not be set correctly. When the
(II) Jan 31 22:16:23 NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
(II) Jan 31 22:16:23 NVIDIA(0): try to use it to receive ACPI event notifications. For
(II) Jan 31 22:16:23 NVIDIA(0): details, please see the "ConnectToAcpid" and
(II) Jan 31 22:16:23 NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
(II) Jan 31 22:16:23 NVIDIA(0): Config Options in the README.
(II) Macintosh mouse button emulation: Device reopened after 1 attempts.
(II) Logitech USB Receiver: Device reopened after 1 attempts.
(II) Logitech USB Receiver: Device reopened after 1 attempts.
(II) Power Button: Device reopened after 1 attempts.
(II) Power Button: Device reopened after 1 attempts.
I'll try without a xorg.conf and post later.

[solved] VSFTPD + Virtual Users + different home directories

Hi All,
I've been trying to get VSFTPD setup to allow ftp access to some of my clients to access their web files. I've got VSFTPD up and running via the Wiki, but my virtual users can't log in. The only thing that I didn't do from the wiki was the "useradd virtual" as I didn't think it was needed. Also, the wiki only covers one directory for all users, I want to have each user to have access to their own web directory and nothing else. I think I may just have something a little off in my vsftpd file. Thanks!
vsftpd.conf
anonymous_enable=NO
local_enable=YES
write_enable=YES
dirmessage_enable=YES
xferlog_enable=YES
connect_from_port_20=YES
data_connection_timeout=120
listen=YES
virtual_use_local_privs=YES
pam_service_name=vsftpd
guest_enable=YES
user_sub_token=$USER
chroot_local_user=YES
hide_ids=YES
local_root=/srv/http/$USER
Last edited by GravityGripp (2009-05-14 17:36:19)

GravityGripp wrote:
I don't think it's a directory permissions issue as it's telling me that my login is incorrect.
Here's my /etc/pam.d/ftp
auth required /lib/security/pam_userdb.so db=/etc/vsftpd_login crypt=hash
account required /lib/security/pam_userdb.so db=/etc/vsftpd_login crypt=hash
here's part of my auth.log also.
May 14 08:14:08 arthur vsftpd: pam_unix(vsftpd:auth): check pass; user unknown
May 14 08:14:08 arthur vsftpd: pam_unix(vsftpd:auth): authentication failure; logname= uid=0 euid=0 tty=ftp ruser=current_user rhost=127.0.0.1
May 14 08:24:14 arthur vsftpd: pam_unix(vsftpd:auth): check pass; user unknown
May 14 08:24:14 arthur vsftpd: pam_unix(vsftpd:auth): authentication failure; logname= uid=0 euid=0 tty=ftp ruser=current_user rhost=127.0.0.1
Hi GravityGripp,
as posted at the beginning of the thread in /etc/vsftpd.conf the 'pam_service_name' option is 'vsftpd' but here you are referencing /etc/pam.d/ftp as PAM service name but in vsftpd.conf you told to use 'vsftpd' as PAM service for auth.
About your need to define different directory for each ftp virtual user in my installation I allow ftp access to virtual users (defined in MySQL and auth via pam_mysql); to let users have access to their own ftp directory (with different auth read only / read-write) I used the user_config_dir option (see man vsftpd.conf).
Here an extract of my '/etc/vsftpd.conf':
# This powerful option allows the override of any config option specified
# in the manual page, on a per-user basis. Usage is simple, and is best
# illustrated with an example. If you set user_config_dir to be /etc/vsftpd_user_conf
# and then log on as the user "chris", then vsftpd will apply the settings
# in the file /etc/vsftpd_user_conf/chris for the duration of the session.
# Default: (none)
user_config_dir=/etc/vsftpd/vsftpd-user-conf
Each time I add a new ftp virtual user that need a personal ftp directory, under the dir '/etc/vsftpd/vsftpd-user-conf' I create a file named as the username where I define the personal ftp directory and the auth on it (RO or RW).
Example for user 'test' (file '/etc/vsftpd/vsftpd-user-conf/test'):
# vsftpd per-user basis config file (override of any config option specified
# in the vsftpd server config file)
# TEMPLATE
# User test - Description for user test
# Set local root
local_root=/srv/vsftpd/test
# Disable any form of FTP write command.
# Allowed values: YES/NO
write_enable=YES
Of course the dir must exist and have the right permissions to allow the user to connect.
Hope that this will be of help.
bye

(solved?) Virtual Box, kernel26-bfs, 1000hz?

I switched to the bfs patched kernel, but I get an error when the kernel tries to load the virtualbox module. I assume this is because the default kernel is using a hz rate higher than 1000. I read 1000 is needed, or else you can break some things like virtual box. My question is how can I set the rate to 1000? I searched the grub page and looked around the bfs documentation and it seems everyone agrees to set the kernel hs to 1000 but how to do it doesn't seem to be discussed.
Sorry for the newbie question!
edit:
I may have solved it. I think I needed to recompile the kernel module and hopefully it will work on my next reboot automatically. I won't know until I reboot, and I can't until tomorrow. I may be back!
Last edited by Google (2010-09-28 12:05:07)

Regarding HZ, you set it in the kernel config when building the package (see the PKGBUILD). Another option is to use ck's patches which change the default from 250 to 1000.
And ... umm ... what is your rate anyways? The default is definitely not more than 1000.
I'm afraid I can't help you with VirtualBox as I know nothing about that.

What is the best way to close a communication session with the FP Server?

Looking at NI's FieldPoint Demobox.vi example, the session is closed by wiring the FP Refnum out from the FP Create Tag vi for the AI module to the FP Close vi. Is there any difference if the FP Refnum out from any or all of the other FP Create Tags were wired to FP Close vi/vi's? Could the FP Refnum out from the FP Open vi be wired to the FP Close vi? What is the best way to do this?
Also, as I'm new to FP and I'm conscious that I might swamp this forum with dumb questions, are the any sources of good FP code examples and/or discussions on coding techniques out there beyond the handful of NI's examples?
Thanks again,
Niel.

Niel,
The FP Open.vi provides a FP Refnum in the form of a data cluster. The cluster contains two elements; a server refnum and a tag refnum. Coming out of the FP Open, only the server refnum has a value, the tag refnum is created when the FP Create Tag.vi is processed. Thus all FP refnums in a process have the same server refnum but different tag refnums. The FP Close.vi uses the server refnum to close the server and ignores the tag refnum so it does not matter which particular refnum was used to close the server. The thing to be careful of is if you close on refnum, you close all refnums. At this point, any reads/writes/advises will result in error 32804 (Invalid IA handle specified).
Also, please swamp this forum with questions. I am in the process of reviewin
g the documentation and examples we provide and having a beginner asking questions that do not appear to be covered in our materials gives me an idea of what we are missing. I would ask that you upgrade to FieldPoint Explorer 2.0.4 and use the online help for LabVIEW since that has had some of my modifications added to it (program flow outlines, vi descriptions & use cases).
Regards, Aaron

What if I close timed-out sessions without calling OCIBreak/OCIReset?

In non-blocking mode it is mentioned in the document that I should call OCIBreak/OCIReset if I want to time-out the session, and these calls will reset the session.
Then, is it ok NOT to call OCIBreak/OCIReset if I want to simply close the timed-out sesion, free everything including the environment handle, and establish everything all over again? Here, each session has its own environment handle and all other threads will keep executing queries within the process. I think my client will clearly be ok to do so, but I'm concerned about possible server-side effects of not OCIBreak/OCIReset the session. Will the sesion be destroyed on the server immediately without client's calling OCIBreak/OCIReset when I destroy everything?

You should call OCIBreak and then disconnect. Last time I checked, OCIBreak performs a TTC OCANCEL operation on the server which would allow you to cleanly disconnect. I'm not sure, but as part of disconnecting, OCI may do this itself. If you don't disconnect cleanly, the server's PMON process will employ dead connection detection (DCD) to determine when to reap your old process. DCD is configurable, but it's best to disconnect cleanly.

[Solved] Close virtual X session?

Similar Messages

Maybe you are looking for