Sponsored Content
Operating Systems Linux Ubuntu Ubuntu creating a new user with Desktop Post 302443765 by rajamadhavan on Tuesday 10th of August 2010 03:38:05 AM
Old 08-10-2010
I think that will be automatically created when the user logs in to the system in run level 5.

useradd will not create the desktop directory.
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Would like to install x86 desktop Ubuntu over AMD64 Ubuntu server

My intention was to build a dual boot XP Pro 64 and Ubuntu media server. I had installed the AMD64 version of Ubuntu 8.10 server and thought that I would be able to install Apache server. I need a GUI to work in. I tried to boot and install Mythbuntu 32 bit 8.10, but my machine now won't recognize... (0 Replies)
Discussion started by: docflyboy
0 Replies

2. Ubuntu

UBUNTU 8.1 Desktop Edition not running after installation

I am a new Ubuntu user, installing Ubuntu on Windows XP . The installation process is successful but after installing when I login , it just freezes with a blank screen for both XClient scripts and GNOME sessions. I have given 10 GB space to the installation. Also i noticed that the time... (5 Replies)
Discussion started by: singla
5 Replies

3. UNIX for Dummies Questions & Answers

How do I link my Ubuntu desktop to a separate partition?

I have a dual boot system on my laptop running Windows 7 professional and Ubuntu 10.10. I would like my windows 7 desktop C:\users\username\Desktop and also my Ubuntu 10.10 desktop /home/username/Desktop to both save their files to the same location somewhere...perhaps /windows (a 40 gb win32... (0 Replies)
Discussion started by: Marcus Aurelius
0 Replies

4. Windows & DOS: Issues & Discussions

Get file on our windows desktop from a ubuntu server

Hello, How can I please have a program automatically upload some files from a ubuntu server to my machine desktop that is running windows XP? I would like to be able to do that from the windows machine itself. Thanks, (3 Replies)
Discussion started by: Pouchie1
3 Replies

5. Ubuntu

How to Get Started on Ubuntu Desktop for the first time

Hello Everyone, I have been using RHEL from quite a while now on server system, but now i also want to use Linux as my Desktop/Laptop OS on my personal computer. So i downloaded the Ubuntu 12.04 yeserday as i have read alot about it being the most popular Linux Desktop OS. So guys could you... (1 Reply)
Discussion started by: Rohit Bhanot
1 Replies

6. Ubuntu

Installing latest Ubuntu on my desktop

I wish to install the latest ubuntu on my desktop. How do I go about doing this ? Also how do I create the superuser or admin once the installation is done ? (3 Replies)
Discussion started by: sundaresh
3 Replies

7. Ubuntu

Ubuntu desktop RAID1 boot problem.

Hello, I installed ubuntu desktop just recently in aim to create a RAID1 configuration using software RAID MDADM. I have the following configuration as fdisk -l reports: Disk /dev/sda: 223,6 GiB, 240057409536 bytes, 468862128 sectors Units: sectors of 1 * 512 = 512 bytes Sector size... (5 Replies)
Discussion started by: Reol
5 Replies
PAM_SYSTEMD(8)							    pam_systemd 						    PAM_SYSTEMD(8)

NAME
pam_systemd - Register user sessions in the systemd login manager SYNOPSIS
pam_systemd.so DESCRIPTION
pam_systemd registers user sessions with the systemd login manager systemd-logind.service(8), and hence the systemd control group hierarchy. On login, this module -- in conjunction with systemd-logind.service -- ensures the following: 1. If it does not exist yet, the user runtime directory /run/user/$UID is either created or mounted as new "tmpfs" file system with quota applied, and its ownership changed to the user that is logging in. 2. The $XDG_SESSION_ID environment variable is initialized. If auditing is available and pam_loginuid.so was run before this module (which is highly recommended), the variable is initialized from the auditing session id (/proc/self/sessionid). Otherwise, an independent session counter is used. 3. A new systemd scope unit is created for the session. If this is the first concurrent session of the user, an implicit per-user slice unit below user.slice is automatically created and the scope placed into it. An instance of the system service user@.service, which runs the systemd user manager instance, is started. On logout, this module ensures the following: 1. If enabled in logind.conf(5) (KillUserProcesses=), all processes of the session are terminated. If the last concurrent session of a user ends, the user's systemd instance will be terminated too, and so will the user's slice unit. 2. If the last concurrent session of a user ends, the user runtime directory /run/user/$UID and all its contents are removed, too. If the system was not booted up with systemd as init system, this module does nothing and immediately returns PAM_SUCCESS. OPTIONS
The following options are understood: class= Takes a string argument which sets the session class. The XDG_SESSION_CLASS environmental variable takes precedence. One of "user", "greeter", "lock-screen" or "background". See sd_session_get_class(3) for details about the session class. type= Takes a string argument which sets the session type. The XDG_SESSION_TYPE environmental variable takes precedence. One of "unspecified", "tty", "x11", "wayland" or "mir". See sd_session_get_type(3) for details about the session type. debug[=] Takes an optional boolean argument. If yes or without the argument, the module will log debugging information as it operates. MODULE TYPES PROVIDED
Only session is provided. ENVIRONMENT
The following environment variables are set for the processes of the user's session: $XDG_SESSION_ID A session identifier, suitable to be used in filenames. The string itself should be considered opaque, although often it is just the audit session ID as reported by /proc/self/sessionid. Each ID will be assigned only once during machine uptime. It may hence be used to uniquely label files or other resources of this session. $XDG_RUNTIME_DIR Path to a user-private user-writable directory that is bound to the user login time on the machine. It is automatically created the first time a user logs in and removed on the user's final logout. If a user logs in twice at the same time, both sessions will see the same $XDG_RUNTIME_DIR and the same contents. If a user logs in once, then logs out again, and logs in again, the directory contents will have been lost in between, but applications should not rely on this behavior and must be able to deal with stale files. To store session-private data in this directory, the user should include the value of $XDG_SESSION_ID in the filename. This directory shall be used for runtime file system objects such as AF_UNIX sockets, FIFOs, PID files and similar. It is guaranteed that this directory is local and offers the greatest possible file system feature set the operating system provides. For further details, see the XDG Base Directory Specification[1]. $XDG_RUNTIME_DIR is not set if the current user is not the original user of the session. The following environment variables are read by the module and may be used by the PAM service to pass metadata to the module: $XDG_SESSION_TYPE The session type. This may be used instead of session= on the module parameter line, and is usually preferred. $XDG_SESSION_CLASS The session class. This may be used instead of class= on the module parameter line, and is usually preferred. $XDG_SESSION_DESKTOP A single, short identifier string for the desktop environment. This may be used to indicate the session desktop used, where this applies and if this information is available. For example: "GNOME", or "KDE". It is recommended to use the same identifiers and capitalization as for $XDG_CURRENT_DESKTOP, as defined by the Desktop Entry Specification[2]. (However, note that $XDG_SESSION_DESKTOP only takes a single item, and not a colon-separated list like $XDG_CURRENT_DESKTOP.) See sd_session_get_desktop(3) for more details. $XDG_SEAT The seat name the session shall be registered for, if any. $XDG_VTNR The VT number the session shall be registered for, if any. (Only applies to seats with a VT available, such as "seat0") EXAMPLE
#%PAM-1.0 auth required pam_unix.so auth required pam_nologin.so account required pam_unix.so password required pam_unix.so session required pam_unix.so session required pam_loginuid.so session required pam_systemd.so SEE ALSO
systemd(1), systemd-logind.service(8), logind.conf(5), loginctl(1), pam.conf(5), pam.d(5), pam(8), pam_loginuid(8), systemd.scope(5), systemd.slice(5), systemd.service(5) NOTES
1. XDG Base Directory Specification http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html 2. Desktop Entry Specification http://standards.freedesktop.org/desktop-entry-spec/latest/ systemd 237 PAM_SYSTEMD(8)
All times are GMT -4. The time now is 01:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy