2 users sources
Hi all, we have a environment with 2 user sources, 1 ad and one e-dir same users in both synked with IDM. The ad is used for vdi users who has windows 7 vdi computer with zenworks client logging in seamless and Novell client loging in the background. Everything well and fine but now i would like to use e-dir as the user source in the vdi environment to.
It's no problem logging in as e-dir user in zenworks but I'm unable to get the seamless login to work.
I have set preferred realm and seamless login in the registry (HKLM) but no joy still logs in as the AD user insted of E-dir.
Is there a other way to force which realm to use?
Best regards
Lennart
I would recommend an SR.
I'm guessing that the preferred user source key is not being picked up
and honored on your VDI setup.
On 5/15/2014 5:06 AM, lelle wrote:
>
> Hi all, we have a environment with 2 user sources, 1 ad and one e-dir
> same users in both synked with IDM. The ad is used for vdi users who has
> windows 7 vdi computer with zenworks client logging in seamless and
> Novell client loging in the background. Everything well and fine but now
> i would like to use e-dir as the user source in the vdi environment to.
> It's no problem logging in as e-dir user in zenworks but I'm unable to
> get the seamless login to work.
> I have set preferred realm and seamless login in the registry (HKLM) but
> no joy still logs in as the AD user insted of E-dir.
> Is there a other way to force which realm to use?
>
> Best regards
>
> Lennart
>
>
Craig Wilson - MCNE, MCSE, CCNA
Novell Technical Support Engineer
Novell does not officially monitor these forums.
Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
Similar Messages
-
Hi all,
We have a concern regarding the user source to be selected at UME level.
At CUP level you can also set the user source for user details.
Our questions here:
1) Is there any relationship between such user source configuration?
2) Which is the best practice here?
Many thanks in advance. Best regards,
ImanolImanol,
if you're setting up UME to use ActiveDirectory as a data source you can set the CUP data source to UME and get at the AD users from CUP.
While I would advise linking UME to AD usually (if you do that there's no need to create users and passwords for new approvers), I would still create an LDAP connector for AD directly in CUP.
Only the LDAP connector will alllow you to use ALL ActiveDirectory fields for custom fields and/or provisioning extended data into your ERP systems (location, room, department etc.).
Frank. -
ZENworks user source login won't go away
Not sure where the best place to put this is.
ZCM 11.2.1
Server 2008R2 - Embedded DB
Win7 Clients - Not sure about XP, we're moving to Win7 only ASAP
Active Directory
When logging into a laptop and NOT connected to the domain LAN, it gets stuck on the Novell ZENworks user source login windows indefinitely. I can try logging into local machine and this happens every time.
In my old environment, with Novell Client, I could click workstation only and get the ZENworks login and cancel.
Not sure what to do to fix this or change the behavior.
Suggestions? TIA!Originally Posted by farmeunitWPSD
Sorry, gave up on getting help with this.
After logging into AD, a "User Source Login" box appears in the upper left. There are no buttons or prompts at that point. Just the box. The box NEVER goes away. If we put the laptops to sleep instead of shutting down, then they can login normally. I found ONE thread about holding SHIFT down before hitting enter after entering login credentials. If they hold SHIFT until the ZENworks login box comes up, then they can cancel that and are logged in fine.
Any chance they're using wireless adapter and have it set to auto-connect?
We have the same thing, but only on Windows XP being reported. Seems it only happens if the person has added a wireless network (XP has slightly diff. options than Windows 7) AND have it set to auto-login/connect. -
ZCM can not connect to user source - LDAP to eDir
Hello all,
We had some issues with our ZCM 10.3.1.0 server this AM. It looks like it was caused by no space on our /var/opt partition.
I had logged in and manually deleted a large old image file. I then restarted the ZCM server. Everything powers on and works as it should except, my user source can not be contacted.
When I try to login with one of my Admin users, we get the following error:
"An error occurred while connecting to the user source. Please make sure the user source is accessible and try again."
If I login as the Administrator of the Zone, I can see that the connection source is not connecting - unable to read contexts. The weird part is that I can connect through LDAP from other tools to the same source on port 636 - JXplorer works just fine.
We are running ZCM on the same server as its database and I can use the LDAP browser built in to SLES 11 x64 and the same LDAP credentials work just fine.
What else can I be looking at?
I am really new to Linux so any help is appreciated.
Steve D.Originally Posted by sjdimare
Hello all,
We had some issues with our ZCM 10.3.1.0 server this AM. It looks like it was caused by no space on our /var/opt partition.
I had logged in and manually deleted a large old image file. I then restarted the ZCM server. Everything powers on and works as it should except, my user source can not be contacted.
When I try to login with one of my Admin users, we get the following error:
"An error occurred while connecting to the user source. Please make sure the user source is accessible and try again."
If I login as the Administrator of the Zone, I can see that the connection source is not connecting - unable to read contexts. The weird part is that I can connect through LDAP from other tools to the same source on port 636 - JXplorer works just fine.
We are running ZCM on the same server as its database and I can use the LDAP browser built in to SLES 11 x64 and the same LDAP credentials work just fine.
What else can I be looking at?
I am really new to Linux so any help is appreciated.
Steve D.
Try removing the user source connection in ZCC and re add it.
Thomas -
Moved user in User Source login prompt
After moving a user in our AD User Source, that user gets prompted for ZCM credentials. I thought this was fixed in a previous version?
ZCM 11.2.4
Server 2012 ADOriginally Posted by farmeunitWPSD
After moving a user in our AD User Source, that user gets prompted for ZCM credentials. I thought this was fixed in a previous version?
ZCM 11.2.4
Server 2012 AD
Try this: https://www.novell.com/support/kb/doc.php?id=7012424
You might need to do a registry change.
Thomas -
Shopping cart not appearing in users sourcing cockpit for completion
Hi
A user cannot see his shopping carts in his sourcing cockpit in his worklist. He finds them with the find tab but he cannot mark them as complete. The completion check box column is not there. However another colleague can find these shooping carts and the completiong column is there. Why this occur?
Does it have anything to do with where the user is placed in the org. struture? Please advise.
Kind regardsHi,
seems that the requirement is assigned to a different Pgroup. Therefore one user does see it, and the other one not. When you adjust the assignment in the Org Model, the user will see the requirement.
Check the responsibility and assignment of your Pgroups.
Cheers,
Claudia -
Setup source of user accounts for WD application.
Hello!
I've got a WD application with "authentificate=true" option deployed on server. User source data for this server is "Database only". I need that WD application should use user accouns from ABAP instance. Is it possible to setup this and only this application for using user accounts from ABAP instance without changing user source data for whole java-instance?
regards, LevHi Lev
Ya it is possible,look
1.In WD authentificate=true gives access to use local system (J2ee Server).
2.For this case some other system (R/3) come into picture as CUA(Central User Administration).use have to call RFC l with definition of the system where user exists.
Check this
A. [Remote Function Call|http://help.sap.com/saphelp_nw04/helpdata/en/05/02cbfa1c2f184eaa6ba151d1aaf4fe/frameset.htm]
B.[how to call RFC!!!|how to call RFC!!!;
Let us know for further details
Best Regards
Satish Kumar -
[SOLVED]MPD, PulseAudio & Systemd/User
Since the advent of skype 4.3 I've had to switch to using pulseaudio. Things seems to be working fine except for the interaction between pulseaudio and mpd. My goal is to attain the same functionality as I had before when I was just using alsa. The main problem seems to be that the mpd daemon starts before pulseaudio. This means that when I reboot, for example, my music doesn't automatically keep playing. However if I toggle mpc (or open ncmpcpp and unpause) then it works fine.
What I have done
1) I installed mpd using the script found on the wiki
1a) copied ~/.config/mpd/mpd.conf to /etc/mpd.conf and uncomment #user line so it runs as my user
1b) enabled the mpd service with systemctl so it starts on boot, as directed to from 1)
2) Applied the workaround detailed here to make pulseaudio play nice with mpd
From what I can understand this results in the mpd daemon using the /etc/mpd.conf file which mirrors my local one (but I think the process is still started as root?)
If I don't do 2) then I get a problem where if I try to open pavucontrol I get an error saying I'm unable to connect and the system feels very unresponsive. Two second delays navigating around in thunar for example.
fuser /dev/snd/* outputs
» sudo fuser /dev/snd/*
/dev/snd/controlC0: 440
/dev/snd/controlC1: 440
/dev/snd/pcmC0D0p: 440m
» ps aux | grep 440
quiv 440 1.2 0.1 495964 13248 ? Sl 15:16 0:05 /usr/bin/pulseaudio --start --log-target=syslog
quiv 2259 0.0 0.0 11668 2296 pts/0 S+ 15:23 0:00 grep --color=auto 440
For now I have added in
if grep -q "state: pause" /home/quiv/.config/mpd/state; then
mpc toggle
fi
to my ~/.xinitrc as a work around to get pulse and mpd to work together properly. However it doesn't seem to work all the time. If I leave my music playing then when I reboot the system with reboot it seems that somtimes the state is being saved as paused, and other times as play. I suppose I could just mpc toggle without checking, but I don't want a situation where if I happen to not be playing music that every time I reboot my music starts playing.
Other things I have tried are;
A) not using pulseaudio with mpd.
B) not using systemd to manage mpd. Instead I manually started it in .xinitrc and pointed it to my ~/.config/mpd/mpd.conf file. I believe this means it runs as my own user instead of as root. When I did this I commented the username line and also undid 2) from above in ~/.config/mpd/mpd.conf
The problem with A) is that if I use alsa with mpd, mpd hogs my soundcard. My card becomes unselectable in pavucontrol and I cannot use it with pulseaudio., meanng no skype. The benefit of doing this (this is how I used to do it before I needed pulseaudio) is I have no problems with mpd's state being saved incorrectly.
The problem with B) is the mpdstate is saved incorrectly when for example I issue reboot. I can reproduce this by changing my currently played song then rebooting. When I boot back up mpd resumes playback from the previous session instead of recognizing the last thing I was playing. I had a search around on the forums and I found this issue which seems to describe what is happening. There doesn't seem to be a solution there instead a suggestion to user systemd (which I would like to do!) instead to manage mpd. Rasi's post details a unit file but I'm unsure what to do with this.
Looking at the wiki it seems like maybe I am supposed to provide this file so that it overwrites the default mpd.service unit. So I followed the steps listed there. First I created the directory /etc/systemd/system/mpd.d/ then made the user.conf file inside. I tried just putting the additional arguments in
[Service]
User=YOUR_USER
PAMName=system-local-login
I also remember trying to overwrite the entire [Service] section of the original by using
[Service]
User=YOUR_USER
PAMName=system-local-login
ExecStart=
ExecStart=/usr/bin/mpd --no-daemon
because I think just adding the addtional parameters might not have worked. But I'm not sure on this point, maybe both ways worked. This seemed to work but I had the same problem as above. The state was still being saved incorrectly sometimes when I rebooted. I would get a previous session instead of the most recent change. So I tried the other method for overwriting systemd unit files and made the file /etc/systemd/system/mpd.service in which I pasted Rasi's entire unit file. This also seemed to work, but still the incorrect state problem happened.
At this point I didn't know what to try. It seemed like the only option left was to set up mpd using a local configuration and setting up a systemd/User session and managing it that way. The wiki indiciated that if I did it this way I would not have to use the method 2) above. However I was/still am hesistant about doing this. I'm new to arch and the systemd/User wiki page seems very intimidating. I worry that I will create problems that I won't understand how to solve using this method just for the chance that mpd will function correclty with pulse. However I seemed to have exhausted all my possible options so I thought whatever I'll try it anyway! I'm certain I probably haven't done it right however.
So once again I turned to the wiki to help me with setting this up. However I can't make sense of the article. I don't know if I should follow ONLY the Setup since systemd 206 or if I should follow both setup sections? I decided to follow only the first section. I use no DE so I commented out the
[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec startx
line in my ~/.zprofile. When I set up my system I followed the Automatic login to virtual console. I left this file alone, but upon second thoughts maybe I should have disabled this too? I don't understand if using xlogin-git to austoart Xorg, as described in the systemd/User page, requires me to get rid of this too. I think xlogin-git just starts Xorg so automatic login via getty should be fine?
Immediately when I boot in using systemd to manage my session I notice that there are problems. I don't think my environment variables are being sourced from .zshenv because my panel fails to load. If I kill the panel and load it again it works. This makes me think there is something wrong with the order of units started with systemd.
» sudo journalctl --this-boot --no-pager | grep -i panel ~
Jul 05 16:25:39 lorelai bash[494]: /home/quiv/.config/bspwm/panel/panel: line 16: : No such file or directory
Jul 05 16:25:39 lorelai bash[494]: /home/quiv/.config/bspwm/panel/panel: line 17: : No such file or directory
Jul 05 16:25:39 lorelai bash[494]: /home/quiv/.config/bspwm/panel/panel: line 18: : No such file or directory
In each instance panel is trying to do things based on $PANEL_FIFO which is exported from ~/.zshenv but it doesn't appear to be set at the time systemd starts things up. Apart from these problems, which are probably undoubtedly due to the fact I failed to set up systemd/User properly, I still have problems with mpd. The state seems to be remembered correctly now, however when I reboot I still have to toggle mpc for it to start playback. It seems to be the same problem as when I use setup detailed intially. I suspect perhaps once again there is something wrong with the order here. MPD starts before pulse so it doesn't find anything to play through, then once I issue the mpc toggle command pulse is started and all is happy.
A final note is that I was getting this error yesterday when using systemd/User
● mpd.service - Music Player Daemon
Loaded: loaded (/usr/lib/systemd/system/mpd.service; enabled)
Active: inactive (dead)
Jul 05 03:11:41 lorelai pulseaudio[450]: [pulseaudio] module-jackdbus-detect.c: Unable to contact D-Bus session bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Jul 05 03:11:41 lorelai pulseaudio[450]: [pulseaudio] module.c: Failed to load module "module-jackdbus-detect" (argument: "channels=2"): initialization failed.
Jul 05 03:11:41 lorelai pulseaudio[450]: [pulseaudio] main.c: Module load failed.
Jul 05 03:13:35 lorelai systemd[1]: Stopping Music Player Daemon...
Jul 05 03:13:35 lorelai systemd[1]: Stopped Music Player Daemon.
but it doesn't seem to happen anymore.
Also I have no idea if I'm even supposed to use it like this but
» sudo systemctl --user enable mpd ~
Failed to get D-Bus connection: Connection refused
I tried this because I was wondering if mpd was even using the correct service when using systemd/User. I thought perhaps it just was using the one in /etc/systemd/system/ instead of /usr/lib/systemd/user/. I'm still not sure about this.
In the end I've exhausted whatever I can think of. I'm sure I've done a lot of things wrong but I tried my best. Hopefully somebody knows what I've done wrong and can help me.
~/.config/mpd/mpd.conf
# An example configuration file for MPD.
# Read the user manual for documentation: http://www.musicpd.org/doc/user/
# Files and directories #######################################################
# This setting controls the top directory which MPD will search to discover the
# available audio files and add them to the daemon's online database. This
# setting defaults to the XDG directory, otherwise the music directory will be
# be disabled and audio files will only be accepted over ipc socket (using
# file:// protocol) or streaming files over an accepted protocol.
music_directory "~/Music"
# This setting sets the MPD internal playlist directory. The purpose of this
# directory is storage for playlists created by MPD. The server will use
# playlist files not created by the server but only if they are in the MPD
# format. This setting defaults to playlist saving being disabled.
playlist_directory "~/.config/mpd/playlists"
# This setting sets the location of the MPD database. This file is used to
# load the database at server start up and store the database while the
# server is not up. This setting defaults to disabled which will allow
# MPD to accept files over ipc socket (using file:// protocol) or streaming
# files over an accepted protocol.
db_file "~/.config/mpd/database"
# These settings are the locations for the daemon log files for the daemon.
# These logs are great for troubleshooting, depending on your log_level
# settings.
# The special value "syslog" makes MPD use the local syslog daemon. This
# setting defaults to logging to syslog, otherwise logging is disabled.
log_file "~/.config/mpd/log"
# This setting sets the location of the file which stores the process ID
# for use of mpd --kill and some init scripts. This setting is disabled by
# default and the pid file will not be stored.
pid_file "~/.config/mpd/pid"
# This setting sets the location of the file which contains information about
# most variables to get MPD back into the same general shape it was in before
# it was brought down. This setting is disabled by default and the server
# state will be reset on server start up.
state_file "~/.config/mpd/state"
# The location of the sticker database. This is a database which
# manages dynamic information attached to songs.
sticker_file "~/.config/mpd/sticker.sql"
# General music daemon options ################################################
# This setting specifies the user that MPD will run as. MPD should never run as
# root and you may use this setting to make MPD change its user ID after
# initialization. This setting is disabled by default and MPD is run as the
# current user.
#user "quiv"
# This setting specifies the group that MPD will run as. If not specified
# primary group of user specified with "user" setting will be used (if set).
# This is useful if MPD needs to be a member of group such as "audio" to
# have permission to use sound card.
#group "nogroup"
# This setting sets the address for the daemon to listen on. Careful attention
# should be paid if this is assigned to anything other then the default, any.
# This setting can deny access to control of the daemon.
# For network
bind_to_address "127.0.0.1"
# And for Unix Socket
bind_to_address "~/.config/mpd/socket"
# This setting is the TCP port that is desired for the daemon to get assigned
# to.
port "6600"
# This setting controls the type of information which is logged. Available
# setting arguments are "default", "secure" or "verbose". The "verbose" setting
# argument is recommended for troubleshooting, though can quickly stretch
# available resources on limited hardware storage.
log_level "default"
# If you have a problem with your MP3s ending abruptly it is recommended that
# you set this argument to "no" to attempt to fix the problem. If this solves
# the problem, it is highly recommended to fix the MP3 files with vbrfix
# (available from <http://www.willwap.co.uk/Programs/vbrfix.php>), at which
# point gapless MP3 playback can be enabled.
gapless_mp3_playback "yes"
# Setting "restore_paused" to "yes" puts MPD into pause mode instead
# of starting playback after startup.
#restore_paused "no"
# This setting enables MPD to create playlists in a format usable by other
# music players.
#save_absolute_paths_in_playlists "no"
# This setting defines a list of tag types that will be extracted during the
# audio file discovery process. The complete list of possible values can be
# found in the mpd.conf man page.
#metadata_to_use "artist,album,title,track,name,genre,date,composer,performer,disc"
# This setting enables automatic update of MPD's database when files in
# music_directory are changed.
auto_update "yes"
# Limit the depth of the directories being watched, 0 means only watch
# the music directory itself. There is no limit by default.
auto_update_depth "3"
# Symbolic link behavior ######################################################
# If this setting is set to "yes", MPD will discover audio files by following
# symbolic links outside of the configured music_directory.
#follow_outside_symlinks "yes"
# If this setting is set to "yes", MPD will discover audio files by following
# symbolic links inside of the configured music_directory.
#follow_inside_symlinks "yes"
# Zeroconf / Avahi Service Discovery ##########################################
# If this setting is set to "yes", service information will be published with
# Zeroconf / Avahi.
#zeroconf_enabled "yes"
# The argument to this setting will be the Zeroconf / Avahi unique name for
# this MPD server on the network.
#zeroconf_name "Music Player"
# Permissions #################################################################
# If this setting is set, MPD will require password authorization. The password
# can setting can be specified multiple times for different password profiles.
#password "password@read,add,control,admin"
# This setting specifies the permissions a user has who has not yet logged in.
#default_permissions "read,add,control,admin"
# Database #######################################################################
#database {
# plugin "proxy"
# host "other.mpd.host"
# port "6600"
# Input #######################################################################
input {
plugin "curl"
proxy "proxy.isp.com:8080"
proxy_user "user"
proxy_password "password"
# Audio Output ################################################################
# MPD supports various audio output types, as well as playing through multiple
# audio outputs at the same time, through multiple audio_output settings
# blocks. Setting this block is optional, though the server will only attempt
# autodetection for one sound card.
# An example of an ALSA output:
#audio_output {
# type "alsa"
# name "My ALSA Device"
## device "hw:0,0" # optional
## mixer_type "hardware" # optional
## mixer_device "default" # optional
## mixer_control "PCM" # optional
## mixer_index "0" # optional
audio_output {
type "pulse"
name "pulse audio"
format "48000:16:2"
## server "127.0.0.1"
## sink "remote_server_sink" # optional
# An example of an OSS output:
#audio_output {
# type "oss"
# name "My OSS Device"
## device "/dev/dsp" # optional
## mixer_type "hardware" # optional
## mixer_device "/dev/mixer" # optional
## mixer_control "PCM" # optional
# An example of a shout output (for streaming to Icecast):
#audio_output {
# type "shout"
# encoding "ogg" # optional
# name "My Shout Stream"
# host "localhost"
# port "8000"
# mount "/mpd.ogg"
# password "hackme"
# quality "5.0"
# bitrate "128"
# format "44100:16:1"
## protocol "icecast2" # optional
## user "source" # optional
## description "My Stream Description" # optional
## url "http://example.com" # optional
## genre "jazz" # optional
## public "no" # optional
## timeout "2" # optional
## mixer_type "software" # optional
# An example of a recorder output:
#audio_output {
# type "recorder"
# name "My recorder"
# encoder "vorbis" # optional, vorbis or lame
# path "/var/lib/mpd/recorder/mpd.ogg"
## quality "5.0" # do not define if bitrate is defined
# bitrate "128" # do not define if quality is defined
# format "44100:16:1"
# An example of a httpd output (built-in HTTP streaming server):
#audio_output {
# type "httpd"
# name "My HTTP Stream"
# encoder "vorbis" # optional, vorbis or lame
# port "8000"
# bind_to_address "0.0.0.0" # optional, IPv4 or IPv6
## quality "5.0" # do not define if bitrate is defined
# bitrate "128" # do not define if quality is defined
# format "44100:16:1"
# max_clients "0" # optional 0=no limit
# An example of a pulseaudio output (streaming to a remote pulseaudio server)
#audio_output {
# type "pulse"
# name "My Pulse Output"
## server "remote_server" # optional
## sink "remote_server_sink" # optional
# An example of a winmm output (Windows multimedia API).
#audio_output {
# type "winmm"
# name "My WinMM output"
## device "Digital Audio (S/PDIF) (High Definition Audio Device)" # optional
# or
## device "0" # optional
## mixer_type "hardware" # optional
# An example of an openal output.
#audio_output {
# type "openal"
# name "My OpenAL output"
## device "Digital Audio (S/PDIF) (High Definition Audio Device)" # optional
## Example "pipe" output:
#audio_output {
# type "pipe"
# name "my pipe"
# command "aplay -f cd 2>/dev/null"
## Or if you're want to use AudioCompress
# command "AudioCompress -m | aplay -f cd 2>/dev/null"
## Or to send raw PCM stream through PCM:
# command "nc example.org 8765"
# format "44100:16:2"
## An example of a null output (for no audio output):
#audio_output {
# type "null"
# name "My Null Output"
# mixer_type "none" # optional
# If MPD has been compiled with libsamplerate support, this setting specifies
# the sample rate converter to use. Possible values can be found in the
# mpd.conf man page or the libsamplerate documentation. By default, this is
# setting is disabled.
#samplerate_converter "Fastest Sinc Interpolator"
# Normalization automatic volume adjustments ##################################
# This setting specifies the type of ReplayGain to use. This setting can have
# the argument "off", "album", "track" or "auto". "auto" is a special mode that
# chooses between "track" and "album" depending on the current state of
# random playback. If random playback is enabled then "track" mode is used.
# See <http://www.replaygain.org> for more details about ReplayGain.
# This setting is off by default.
replaygain "album"
# This setting sets the pre-amp used for files that have ReplayGain tags. By
# default this setting is disabled.
replaygain_preamp "0"
# This setting sets the pre-amp used for files that do NOT have ReplayGain tags.
# By default this setting is disabled.
#replaygain_missing_preamp "0"
# This setting enables or disables ReplayGain limiting.
# MPD calculates actual amplification based on the ReplayGain tags
# and replaygain_preamp / replaygain_missing_preamp setting.
# If replaygain_limit is enabled MPD will never amplify audio signal
# above its original level. If replaygain_limit is disabled such amplification
# might occur. By default this setting is enabled.
#replaygain_limit "yes"
# This setting enables on-the-fly normalization volume adjustment. This will
# result in the volume of all playing audio to be adjusted so the output has
# equal "loudness". This setting is disabled by default.
#volume_normalization "no"
# MPD Internal Buffering ######################################################
# This setting adjusts the size of internal decoded audio buffering. Changing
# this may have undesired effects. Don't change this if you don't know what you
# are doing.
#audio_buffer_size "4096"
# This setting controls the percentage of the buffer which is filled before
# beginning to play. Increasing this reduces the chance of audio file skipping,
# at the cost of increased time prior to audio playback.
#buffer_before_play "10%"
# Resource Limitations ########################################################
# These settings are various limitations to prevent MPD from using too many
# resources. Generally, these settings should be minimized to prevent security
# risks, depending on the operating resources.
#connection_timeout "60"
#max_connections "10"
#max_playlist_length "16384"
#max_command_list_size "2048"
#max_output_buffer_size "8192"
# Character Encoding ##########################################################
# If file or directory names do not display correctly for your locale then you
# may need to modify this setting.
#filesystem_charset "UTF-8"
# This setting controls the encoding that ID3v1 tags should be converted from.
#id3v1_encoding "ISO-8859-1"
# SIDPlay decoder #############################################################
# songlength_database:
# Location of your songlengths file, as distributed with the HVSC.
# The sidplay plugin checks this for matching MD5 fingerprints.
# See http://www.c64.org/HVSC/DOCUMENTS/Songlengths.faq
# default_songlength:
# This is the default playing time in seconds for songs not in the
# songlength database, or in case you're not using a database.
# A value of 0 means play indefinitely.
# filter:
# Turns the SID filter emulation on or off.
#decoder {
# plugin "sidplay"
# songlength_database "/media/C64Music/DOCUMENTS/Songlengths.txt"
# default_songlength "120"
# filter "true"
/etc/mpd.config
# An example configuration file for MPD.
# Read the user manual for documentation: http://www.musicpd.org/doc/user/
# Files and directories #######################################################
# This setting controls the top directory which MPD will search to discover the
# available audio files and add them to the daemon's online database. This
# setting defaults to the XDG directory, otherwise the music directory will be
# be disabled and audio files will only be accepted over ipc socket (using
# file:// protocol) or streaming files over an accepted protocol.
music_directory "~/Music"
# This setting sets the MPD internal playlist directory. The purpose of this
# directory is storage for playlists created by MPD. The server will use
# playlist files not created by the server but only if they are in the MPD
# format. This setting defaults to playlist saving being disabled.
playlist_directory "~/.config/mpd/playlists"
# This setting sets the location of the MPD database. This file is used to
# load the database at server start up and store the database while the
# server is not up. This setting defaults to disabled which will allow
# MPD to accept files over ipc socket (using file:// protocol) or streaming
# files over an accepted protocol.
db_file "~/.config/mpd/database"
# These settings are the locations for the daemon log files for the daemon.
# These logs are great for troubleshooting, depending on your log_level
# settings.
# The special value "syslog" makes MPD use the local syslog daemon. This
# setting defaults to logging to syslog, otherwise logging is disabled.
log_file "~/.config/mpd/log"
# This setting sets the location of the file which stores the process ID
# for use of mpd --kill and some init scripts. This setting is disabled by
# default and the pid file will not be stored.
pid_file "~/.config/mpd/pid"
# This setting sets the location of the file which contains information about
# most variables to get MPD back into the same general shape it was in before
# it was brought down. This setting is disabled by default and the server
# state will be reset on server start up.
state_file "~/.config/mpd/state"
# The location of the sticker database. This is a database which
# manages dynamic information attached to songs.
sticker_file "~/.config/mpd/sticker.sql"
# General music daemon options ################################################
# This setting specifies the user that MPD will run as. MPD should never run as
# root and you may use this setting to make MPD change its user ID after
# initialization. This setting is disabled by default and MPD is run as the
# current user.
user "quiv"
# This setting specifies the group that MPD will run as. If not specified
# primary group of user specified with "user" setting will be used (if set).
# This is useful if MPD needs to be a member of group such as "audio" to
# have permission to use sound card.
#group "nogroup"
# This setting sets the address for the daemon to listen on. Careful attention
# should be paid if this is assigned to anything other then the default, any.
# This setting can deny access to control of the daemon.
# For network
bind_to_address "127.0.0.1"
# And for Unix Socket
bind_to_address "~/.config/mpd/socket"
# This setting is the TCP port that is desired for the daemon to get assigned
# to.
port "6600"
# This setting controls the type of information which is logged. Available
# setting arguments are "default", "secure" or "verbose". The "verbose" setting
# argument is recommended for troubleshooting, though can quickly stretch
# available resources on limited hardware storage.
log_level "default"
# If you have a problem with your MP3s ending abruptly it is recommended that
# you set this argument to "no" to attempt to fix the problem. If this solves
# the problem, it is highly recommended to fix the MP3 files with vbrfix
# (available from <http://www.willwap.co.uk/Programs/vbrfix.php>), at which
# point gapless MP3 playback can be enabled.
gapless_mp3_playback "yes"
# Setting "restore_paused" to "yes" puts MPD into pause mode instead
# of starting playback after startup.
#restore_paused "no"
# This setting enables MPD to create playlists in a format usable by other
# music players.
#save_absolute_paths_in_playlists "no"
# This setting defines a list of tag types that will be extracted during the
# audio file discovery process. The complete list of possible values can be
# found in the mpd.conf man page.
#metadata_to_use "artist,album,title,track,name,genre,date,composer,performer,disc"
# This setting enables automatic update of MPD's database when files in
# music_directory are changed.
auto_update "yes"
# Limit the depth of the directories being watched, 0 means only watch
# the music directory itself. There is no limit by default.
auto_update_depth "3"
# Symbolic link behavior ######################################################
# If this setting is set to "yes", MPD will discover audio files by following
# symbolic links outside of the configured music_directory.
#follow_outside_symlinks "yes"
# If this setting is set to "yes", MPD will discover audio files by following
# symbolic links inside of the configured music_directory.
#follow_inside_symlinks "yes"
# Zeroconf / Avahi Service Discovery ##########################################
# If this setting is set to "yes", service information will be published with
# Zeroconf / Avahi.
#zeroconf_enabled "yes"
# The argument to this setting will be the Zeroconf / Avahi unique name for
# this MPD server on the network.
#zeroconf_name "Music Player"
# Permissions #################################################################
# If this setting is set, MPD will require password authorization. The password
# can setting can be specified multiple times for different password profiles.
#password "password@read,add,control,admin"
# This setting specifies the permissions a user has who has not yet logged in.
#default_permissions "read,add,control,admin"
# Database #######################################################################
#database {
# plugin "proxy"
# host "other.mpd.host"
# port "6600"
# Input #######################################################################
input {
plugin "curl"
proxy "proxy.isp.com:8080"
proxy_user "user"
proxy_password "password"
# Audio Output ################################################################
# MPD supports various audio output types, as well as playing through multiple
# audio outputs at the same time, through multiple audio_output settings
# blocks. Setting this block is optional, though the server will only attempt
# autodetection for one sound card.
# An example of an ALSA output:
#audio_output {
# type "alsa"
# name "My ALSA Device"
## device "hw:0,0" # optional
## mixer_type "hardware" # optional
## mixer_device "default" # optional
## mixer_control "PCM" # optional
## mixer_index "0" # optional
audio_output {
type "pulse"
name "pulse audio"
format "48000:16:2"
server "127.0.0.1"
## sink "remote_server_sink" # optional
# An example of an OSS output:
#audio_output {
# type "oss"
# name "My OSS Device"
## device "/dev/dsp" # optional
## mixer_type "hardware" # optional
## mixer_device "/dev/mixer" # optional
## mixer_control "PCM" # optional
# An example of a shout output (for streaming to Icecast):
#audio_output {
# type "shout"
# encoding "ogg" # optional
# name "My Shout Stream"
# host "localhost"
# port "8000"
# mount "/mpd.ogg"
# password "hackme"
# quality "5.0"
# bitrate "128"
# format "44100:16:1"
## protocol "icecast2" # optional
## user "source" # optional
## description "My Stream Description" # optional
## url "http://example.com" # optional
## genre "jazz" # optional
## public "no" # optional
## timeout "2" # optional
## mixer_type "software" # optional
# An example of a recorder output:
#audio_output {
# type "recorder"
# name "My recorder"
# encoder "vorbis" # optional, vorbis or lame
# path "/var/lib/mpd/recorder/mpd.ogg"
## quality "5.0" # do not define if bitrate is defined
# bitrate "128" # do not define if quality is defined
# format "44100:16:1"
# An example of a httpd output (built-in HTTP streaming server):
#audio_output {
# type "httpd"
# name "My HTTP Stream"
# encoder "vorbis" # optional, vorbis or lame
# port "8000"
# bind_to_address "0.0.0.0" # optional, IPv4 or IPv6
## quality "5.0" # do not define if bitrate is defined
# bitrate "128" # do not define if quality is defined
# format "44100:16:1"
# max_clients "0" # optional 0=no limit
# An example of a pulseaudio output (streaming to a remote pulseaudio server)
#audio_output {
# type "pulse"
# name "My Pulse Output"
## server "remote_server" # optional
## sink "remote_server_sink" # optional
# An example of a winmm output (Windows multimedia API).
#audio_output {
# type "winmm"
# name "My WinMM output"
## device "Digital Audio (S/PDIF) (High Definition Audio Device)" # optional
# or
## device "0" # optional
## mixer_type "hardware" # optional
# An example of an openal output.
#audio_output {
# type "openal"
# name "My OpenAL output"
## device "Digital Audio (S/PDIF) (High Definition Audio Device)" # optional
## Example "pipe" output:
#audio_output {
# type "pipe"
# name "my pipe"
# command "aplay -f cd 2>/dev/null"
## Or if you're want to use AudioCompress
# command "AudioCompress -m | aplay -f cd 2>/dev/null"
## Or to send raw PCM stream through PCM:
# command "nc example.org 8765"
# format "44100:16:2"
## An example of a null output (for no audio output):
#audio_output {
# type "null"
# name "My Null Output"
# mixer_type "none" # optional
# If MPD has been compiled with libsamplerate support, this setting specifies
# the sample rate converter to use. Possible values can be found in the
# mpd.conf man page or the libsamplerate documentation. By default, this is
# setting is disabled.
#samplerate_converter "Fastest Sinc Interpolator"
# Normalization automatic volume adjustments ##################################
# This setting specifies the type of ReplayGain to use. This setting can have
# the argument "off", "album", "track" or "auto". "auto" is a special mode that
# chooses between "track" and "album" depending on the current state of
# random playback. If random playback is enabled then "track" mode is used.
# See <http://www.replaygain.org> for more details about ReplayGain.
# This setting is off by default.
replaygain "album"
# This setting sets the pre-amp used for files that have ReplayGain tags. By
# default this setting is disabled.
replaygain_preamp "0"
# This setting sets the pre-amp used for files that do NOT have ReplayGain tags.
# By default this setting is disabled.
#replaygain_missing_preamp "0"
# This setting enables or disables ReplayGain limiting.
# MPD calculates actual amplification based on the ReplayGain tags
# and replaygain_preamp / replaygain_missing_preamp setting.
# If replaygain_limit is enabled MPD will never amplify audio signal
# above its original level. If replaygain_limit is disabled such amplification
# might occur. By default this setting is enabled.
#replaygain_limit "yes"
# This setting enables on-the-fly normalization volume adjustment. This will
# result in the volume of all playing audio to be adjusted so the output has
# equal "loudness". This setting is disabled by default.
#volume_normalization "no"
# MPD Internal Buffering ######################################################
# This setting adjusts the size of internal decoded audio buffering. Changing
# this may have undesired effects. Don't change this if you don't know what you
# are doing.
#audio_buffer_size "4096"
# This setting controls the percentage of the buffer which is filled before
# beginning to play. Increasing this reduces the chance of audio file skipping,
# at the cost of increased time prior to audio playback.
#buffer_before_play "10%"
# Resource Limitations ########################################################
# These settings are various limitations to prevent MPD from using too many
# resources. Generally, these settings should be minimized to prevent security
# risks, depending on the operating resources.
#connection_timeout "60"
#max_connections "10"
#max_playlist_length "16384"
#max_command_list_size "2048"
#max_output_buffer_size "8192"
# Character Encoding ##########################################################
# If file or directory names do not display correctly for your locale then you
# may need to modify this setting.
#filesystem_charset "UTF-8"
# This setting controls the encoding that ID3v1 tags should be converted from.
#id3v1_encoding "ISO-8859-1"
# SIDPlay decoder #############################################################
# songlength_database:
# Location of your songlengths file, as distributed with the HVSC.
# The sidplay plugin checks this for matching MD5 fingerprints.
# See http://www.c64.org/HVSC/DOCUMENTS/Songlengths.faq
# default_songlength:
# This is the default playing time in seconds for songs not in the
# songlength database, or in case you're not using a database.
# A value of 0 means play indefinitely.
# filter:
# Turns the SID filter emulation on or off.
#decoder {
# plugin "sidplay"
# songlength_database "/media/C64Music/DOCUMENTS/Songlengths.txt"
# default_songlength "120"
# filter "true"
/etc/X11/xinit/xinitrc.d/pulseaudio [not sure if I even need this?]
#!/bin/bash
case "$DESKTOP_SESSION" in
gnome|kde*|xfce*) # PulseAudio is started via XDG Autostart
# Extra checks in case DESKTOP_SESSION is not set correctly
if [[ -z $KDE_FULL_SESSION && -z $GNOME_DESKTOP_SESSION_ID ]]; then
/usr/bin/start-pulseaudio-x11
fi
esac
/etc/pulse/daemon.conf
# This file is part of PulseAudio.
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
# USA.
## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out. Use either ; or # for
## commenting.
; daemonize = no
; fail = yes
; allow-module-loading = yes
; allow-exit = yes
; use-pid-file = yes
; system-instance = no
; local-server-type = user
; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 MiB
; lock-memory = no
; cpu-limit = no
; high-priority = yes
; nice-level = -11
; realtime-scheduling = yes
; realtime-priority = 5
exit-idle-time=0
; exit-idle-time = 20
; scache-idle-time = 20
; dl-search-path = (depends on architecture)
; load-default-script-file = yes
; default-script-file = /etc/pulse/default.pa
; log-target = auto
log-level = error
; log-meta = no
; log-time = no
; log-backtrace = 0
resample-method = speex-float-7
; enable-remixing = yes
; enable-lfe-remixing = no
flat-volumes = no
; rlimit-fsize = -1
; rlimit-data = -1
; rlimit-stack = -1
; rlimit-core = -1
; rlimit-as = -1
; rlimit-rss = -1
; rlimit-nproc = -1
; rlimit-nofile = 256
; rlimit-memlock = -1
; rlimit-locks = -1
; rlimit-sigpending = -1
; rlimit-msgqueue = -1
; rlimit-nice = 31
; rlimit-rtprio = 9
; rlimit-rttime = 1000000
default-sample-format = s24le
default-sample-rate = 48000
; alternate-sample-rate = 48000
; default-sample-channels = 2
; default-channel-map = front-left,front-right
default-fragments = 2
default-fragment-size-msec = 76
; enable-deferred-volume = yes
; deferred-volume-safety-margin-usec = 8000
; deferred-volume-extra-delay-usec = 0
/etc/pulse/default.pa
#!/usr/bin/pulseaudio -nF
# This file is part of PulseAudio.
# PulseAudio is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, write to the Free Software Foundation,
# Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.
# This startup script is used only if PulseAudio is started per-user
# (i.e. not in system mode)
.nofail
### Load something into the sample cache
#load-sample-lazy x11-bell /usr/share/sounds/gtk-events/activate.wav
#load-sample-lazy pulse-hotplug /usr/share/sounds/startup3.wav
#load-sample-lazy pulse-coldplug /usr/share/sounds/startup3.wav
#load-sample-lazy pulse-access /usr/share/sounds/generic.wav
.fail
### Automatically restore the volume of streams and devices
load-module module-device-restore
load-module module-stream-restore
load-module module-card-restore
### Automatically augment property information from .desktop files
### stored in /usr/share/application
load-module module-augment-properties
### Should be after module-*-restore but before module-*-detect
load-module module-switch-on-port-available
### Load audio drivers statically
### (it's probably better to not load these drivers manually, but instead
### use module-udev-detect -- see below -- for doing this automatically)
#load-module module-alsa-sink
#load-module module-alsa-source device=hw:1,0
#load-module module-oss device="/dev/dsp" sink_name=output source_name=input
#load-module module-oss-mmap device="/dev/dsp" sink_name=output source_name=input
#load-module module-null-sink
#load-module module-pipe-sink
### Automatically load driver modules depending on the hardware available
.ifexists module-udev-detect.so
load-module module-udev-detect
.else
### Use the static hardware detection module (for systems that lack udev support)
load-module module-detect
.endif
### Automatically connect sink and source if JACK server is present
.ifexists module-jackdbus-detect.so
.nofail
load-module module-jackdbus-detect channels=2
.fail
.endif
### Automatically load driver modules for Bluetooth hardware
#.ifexists module-bluetooth-policy.so
#load-module module-bluetooth-policy
#.endif
#.ifexists module-bluetooth-discover.so
#load-module module-bluetooth-discover
#.endif
### Load several protocols
.ifexists module-esound-protocol-unix.so
load-module module-esound-protocol-unix
.endif
load-module module-native-protocol-unix
### Network access (may be configured with paprefs, so leave this commented
### here if you plan to use paprefs)
#load-module module-esound-protocol-tcp
load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1
#load-module module-zeroconf-publish
### Load the RTP receiver module (also configured via paprefs, see above)
#load-module module-rtp-recv
### Load the RTP sender module (also configured via paprefs, see above)
#load-module module-null-sink sink_name=rtp format=s16be channels=2 rate=44100 sink_properties="device.description='RTP Multicast Sink'"
#load-module module-rtp-send source=rtp.monitor
### Load additional modules from GConf settings. This can be configured with the paprefs tool.
### Please keep in mind that the modules configured by paprefs might conflict with manually
### loaded modules.
.ifexists module-gconf.so
.nofail
load-module module-gconf
.fail
.endif
### Automatically restore the default sink/source when changed by the user
### during runtime
### NOTE: This should be loaded as early as possible so that subsequent modules
### that look up the default sink/source get the right value
load-module module-default-device-restore
### Automatically move streams to the default sink if the sink they are
### connected to dies, similar for sources
load-module module-rescue-streams
### Make sure we always have a sink around, even if it is a null sink.
load-module module-always-sink
### Honour intended role device property
load-module module-intended-roles
### Automatically suspend sinks/sources that become idle for too long
load-module module-suspend-on-idle
### If autoexit on idle is enabled we want to make sure we only quit
### when no local session needs us anymore.
.ifexists module-console-kit.so
load-module module-console-kit
.endif
.ifexists module-systemd-login.so
load-module module-systemd-login
.endif
### Enable positioned event sounds
load-module module-position-event-sounds
### Cork music/video streams when a phone stream is active
load-module module-role-cork
### Modules to allow autoloading of filters (such as echo cancellation)
### on demand. module-filter-heuristics tries to determine what filters
### make sense, and module-filter-apply does the heavy-lifting of
### loading modules and rerouting streams.
load-module module-filter-heuristics
load-module module-filter-apply
# X11 modules should not be started from default.pa so that one daemon
# can be shared by multiple sessions.
### Load X11 bell module
#load-module module-x11-bell sample=bell-windowing-system
### Register ourselves in the X11 session manager
#load-module module-x11-xsmp
### Publish connection data in the X11 root window
#.ifexists module-x11-publish.so
#.nofail
#load-module module-x11-publish
#.fail
#.endif
### Make some devices default
#set-default-sink output
#set-default-source input
~/.xinitrc [currently using daemon mpd]
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
#if grep -q "state: pause" /home/quiv/.config/mpd/state; then
# mpc toggle
#fi
#mpd ~/.config/mpd/mpd.conf
~/.config/bspwm/panel/notify_mpd
xrdb ~/.Xresources
xset +fp ~/.fonts
xset +fp /usr/share/fonts/misc
xset fp rehash
xsetroot -cursor_name left_ptr &
# imlibsetroot -x e -s f /home/quiv/Pictures/bloom_one_desktop.jpg
sh ~/.fehbg &
compton -CGb --backend glx --paint-on-overlay --vsync opengl-swc &
# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
sxhkd &
exec bspwm
~/.zprofile [currently trying to use systemd/User]
#[[ -z $DISPLAY && $XDG_VTNR -eq 1 ]] && exec startx
EDIT:A small update; it seems I don't need to have /etc/systemd/system/[email protected]/autologin.conf when using systemd to manag my user session as I removed it and I'm both automatically logged on and in X-session.
Last edited by quiv (2014-07-05 13:40:30)o_caino wrote:
Setting mpd as a systemd user service is very simple. This is what I did.
In ~/.config/systemd/user/mpd.service
[Unit]
Description=Music Player Daemon
After=network.target sound.target
[Service]
ExecStart=/usr/bin/mpd --no-daemon
ExecStop=/usr/bin/mpd --kill
[Install]
WantedBy=default.target
To enable
systemctl --user enable mpd
Done.
Well shit. I guess I didn't need to do all that other stuff. I only wish I'd known about this before wasting most of my day. Thank you very much, everything appears to be working flawlessly now. -
Re: (forte-users) Oggetto: Re: (forte-users) mouseCursors
Luca,
Forte makes use of mouse settings on the machine on which
the app is being run.
You can ad custom cursors by making the default
cursor schemes use your bitmaps( Windows/Control Panel/ Mouse ).
But when you deploy your app, if the client machine(s)
has a different setting, you will not see your
custom cursors.
I don't know if there is a way in Forte to tweak
Mouse settings on client machines. Even if there was a
way, how would you add the the custom cursor(s) to
app distribution??
Ajith Kallambella M.
Forte Consultant.
From: Luca Gioppo <[email protected]>
To: [email protected]
CC: [email protected]
Subject: (forte-users) Oggetto: Re: (forte-users) mouse Cursors
Date: Tue, 19 Oct 1999 17:20:00 +0200
Aready tryed, but with 'sad' result.
My application run under win '95 and cursors look really .. lets say
umpleasant.
I'd like to have a bitmap of mine or something like that.
Hoped that things like that were not so difficult, even with some
costraint.
Luca
For the archives, go to: http://lists.sageit.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]I went through the same process some time back. I
submitted a call to Forte and was informed that there
are hooks but they were intentionally undocumented
because Forte had plans to provide a interface to
Source Control Managers in future releases. If you
submit a call, they will send you a ZIP file
containing instructions on how to use the hooks. The
hooks have proven very useful.
--- Luca Gioppo <Luca.Gioppocsi.it> wrote:
>
>
I think that the topic is still open and alive.
In my case I have the need to integrate with PVCS
dimension.
The problem for me is that we develop both with java
and tool, and is
frustrating seeing java people smiling as tha
various tools give the chance to
integrate to various extends with source control
products.
I'm interested too in the problem, looking for a
solution since a bit, but no
satifactory solutions.
So count 2 on the problem.
Luca
"David Potts" <david.pottss1.com> il 23/11/2000
17.12.47
Per: forte-userslists.xpedior.com
cc: (ccr: Luca Gioppo/CSI/IT)
Oggetto: (forte-users) Source Control
Hello,
I'm looking how to do version control for forte
development, and have
done a search on the list archive. There are lots
of messages asking
how to do source control, but the answers all seem
to be "roll your
own". My questions are:
(1) Most of the postings seem to come from some
years ago. What is the
current state of play with source control for forte
4GL?
(2) There was some mention of "hooks". What are
these hooks?
(3) With Sun appearing on the scene, anyone got any
idea where source
control is going in future versions?
I'm very new to Forte, so sorry if this topic has
been closed.
Cheers,
Dave.
ATTACHMENT part 2 application/octet-streamname=david.potts.vcf
http://shopping.yahoo.com/ -
User created in ECC system does not appear in Identity management
Hi all,
For the already new built GRC system, I am trying to configure buidling blocks 678: RiskAnalysis and Remediation.
1- In section 5.2 (5.2 Add Roles to Existing Users in User Management Engine) I have to add roles to the users which were created in ECC system. But in Identity management I could not see those ID's existing.
2 - I could not see these roles RE_ADMIN and CC_ADMIN in UME
Could anybody help me moving forward.
Thanks
LakshmiHi,
> 1- In section 5.2 (5.2 Add Roles to Existing Users in User Management Engine) I have to add roles to the users which were >created in ECC system. But in Identity management I could not see those ID's existing.
>
Have you defined Master User Source in RAR ?
> 2 - I could not see these roles RE_ADMIN and CC_ADMIN in UME
>
Initially you have to upload Roles in Identity management. There will be 3 files:
cc_ume_roles.txt
ae_ume_roles.txt
re_ume_roles.txt
Upload them in identity management then you will get these roles.
Thanks
Sunny -
GRC 5.3 CUP SP16 - User info not loading from LDAP into CUP
Hello,
We have multiple LDAPS that we needed to connect to our CUP system to authenticate the userids before a request can be created for them. And also to bring in Manager ID and manager email from LDAP as the first level approver for requests.
My client hasn't maintained the actual LDAP userids, Manager and manager email fields correctly, so we utlized three other custom fields in LDAP and then did field mapping in CUP for those fields. But even when the connection to all the LDAPs is successful, there's no user information being pulled in from LDAP into CUP. I noticed that when I use our backend SAP QA system as 'User Data Source' while using multiple LDAPS for 'User Detail Source Data' , it only reads data from SAP QA system SU01 area and even when I'm trying to create requests, no Manager info is being pulled from LDAPS for that user id.
SAP does not allow the use of multiple LDAPS for the configuration-->User Data Source , top option. So, if a client has userids in multiple systems, it can only read from one data source. But even when I temporarily assigned one active directory LDAP to the 'user data source' option, it stated, no records found. So, something is up that no data is being pulled from LDAPs even when the connection to those systems is successful. I just asked our AD guy to temporarily assign domain admin rights to that LDAP connection ID to see if it's access issue, and still I am not getting any LDAP data to read into GRC CUP.
Anyone else has had this issue? Is there especial access that the LDAP connection id needs access in LDAP to be able to retreive data into GRC? Is there any jobs that need to be run to read LDAP data. I thought it should be live as the system is connected to LDAPs. I don't understand if the connection is successful, why the user info is not being pulled from there and even after the LDAP custom field mapping is done, those field values are not showing up on requests.
We need the following to happen:
1). Authenticate the custom userid field in LDAPs to ensure this user exist as an employee b4 request can be created for the user. For this I have configured the multiple LDAPS for the 'Authentication'. But it doesn't seem to confirm that option when creating a request for a user.
2). The user details info source should bring in the custom manager id and manager email into the request to send the first level of approval via workflow to that manager. Since SAP doesn't give the option to define approvers per user group values in CUP, we had to actually map all the User Owner approvers this way since their direct managers are not aware of what to request as the User owner approvers per user group are. So, we added custom fields for Manager id and Manager EMail into LDAP to be ready automatically into the request when reading user id while creating request.
I will greatly appreciate anyone's help on how they got the LDAP field values to be read into GRC CUP for request processing and what type of encripted access can a LDAP connection id have without assigning it complete domain admin rights on an open port 389 for LDAP and GRC CUP connection.
Thanks and Regards,
AlleyHi Alley,
1). Authenticate the custom userid field in LDAPs to ensure this user exist as an employee b4 request can be created for the user. For this I have configured the multiple LDAPS for the 'Authentication'. But it doesn't seem to confirm that option when creating a request for a user.
This is not possible. You can have only 1 LDAP. Why you want to authenticate the user in different sources?? CUP looks at only one user source, not many. The below wiki explains you the configuration part:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b089fb71-a3b7-2a10-64a2-8c77243b0664
2). The user details info source should bring in the custom manager id and manager email into the request to send the first level of approval via workflow to that manager. Since SAP doesn't give the option to define approvers per user group values in CUP, we had to actually map all the User Owner approvers this way since their direct managers are not aware of what to request as the User owner approvers per user group are. So, we added custom fields for Manager id and Manager EMail into LDAP to be ready automatically into the request when reading user id while creating request.
Based on user group is not possible. However, if you wish to maintain the Manager's Field, ensure that the CUP mapping is done correctly from the Configuration, Field Mapping, LDAP Mapping.
While defining the workflow, take the approver determinator as Manager. This will route the request to the users manager. Also, ensure that LDAP is the source in all the confiuration areas in CUP.
Check note 1228996 for more information.
Hope this helps!!
Regards,
Raghu -
Using the Repository hooks, one can trap workspace integrations and create
.cex and .pex files of the changed objects, which can be read into the SCM
tool. Right?
But how do you handle the situation where a class has been renamed? How do
you deal with all those other classes that have attributes that are of this
renamed class type? What if you want the full source code of 6 weeks ago,
before several big changes including class renames? Can you then recreate a
complete .wex file, where all the changes before 6 weeks ago are included,
but all changes since 6 weeks ago are excluded?
Is is perhaps more feasible to create a full .wex file every day, or every
week, and store that in an SCM tool? But then, what's the use of these
repository hooks?
Pascal Rottier
Atos Origin Nederland (BAS/West End User Computing)
Tel. +31 (0)10-2661223
Fax. +31 (0)10-2661199
E-mail: Pascal.Rottiernl.origin-it.com
++++++++++++++++++++++++++++
Philip Morris (Afd. MIS)
Tel. +31 (0)164-295149
Fax. +31 (0)164-294444
E-mail: Rottier.Pascalpmintl.chIt sounds like you simply store the whole repository file in your SCM. How
else do you store partitioning schemes, which can't be exported as far as I
know.
Pascal Rottier
Atos Origin Nederland (BAS/West End User Computing)
Tel. +31 (0)10-2661223
Fax. +31 (0)10-2661199
E-mail: Pascal.Rottiernl.origin-it.com
++++++++++++++++++++++++++++
Philip Morris (Afd. MIS)
Tel. +31 (0)164-295149
Fax. +31 (0)164-294444
E-mail: Rottier.Pascalpmintl.ch
-----Original Message-----
From: Roland Ottersbach [mailto:roparcs.de]
Sent: Monday, November 27, 2000 9:06 PM
To: Rottier, Pascal
Cc: 'Forte Users'
Subject: Re: (forte-users) Source Control continued...
Hi everyone,
I'd like to take part of this discussion, as we developed a integration to
continuus configuration management suite
from continuus software. This integration goes beyond simple version control
system. It handles the software
issues as any other integration using the SCM-Hook. But it overs a lot more:
As Continuus overs as one of a few providers task based CM we support full
support of task based CM as
simple as it gets. The more we handle different releases of software
products.
The integration takes care of partition informations as well, so that with
your
sources the deployment information
and the application information is stored and can be restored any time.
Guess
you have to go back to a former
release of your product and you have released this software to certain
customers: You would like to restore your
software at that point completely, including partition information. We can
do
this.
But the best thing about this integration is, that you don't care about
retrieving your software out of the CM Tool manually
and place it back in a production repository. The integration cares for this
too. By a click you get a brand new repository
at any release you've integrated before and want to go back to as a manner
of
maintanance or merging.
Fell free to contact me, if you like.
We've choosen Continuus, because we know it a long time. Is very powerful
but
sometimes a little bit sophisticated
too. Nevertheless it overs a lot of things you would like to use, if you go
deep into configuration and change management.
Regards
Roland Ottersbach
Workflow and Change Management
parcs IT-Consulting GmbH (ww.parcs.de)
Birlenbacher Strasse 14 K
Germany
eMail roparcs.de
Mobile 0049 (0) 171 374 5171
Telefon 0049 (0) 271 870 6421
"Rottier, Pascal" schrieb:
Using the Repository hooks, one can trap workspace integrations and create
.cex and .pex files of the changed objects, which can be read into the SCM
tool. Right?
But how do you handle the situation where a class has been renamed? How do
you deal with all those other classes that have attributes that are ofthis
renamed class type? What if you want the full source code of 6 weeks ago,
before several big changes including class renames? Can you then recreatea
complete .wex file, where all the changes before 6 weeks ago are included,
but all changes since 6 weeks ago are excluded?
Is is perhaps more feasible to create a full .wex file every day, or every
week, and store that in an SCM tool? But then, what's the use of these
repository hooks?
Pascal Rottier
Atos Origin Nederland (BAS/West End User Computing)
Tel. +31 (0)10-2661223
Fax. +31 (0)10-2661199
E-mail: Pascal.Rottiernl.origin-it.com
++++++++++++++++++++++++++++
Philip Morris (Afd. MIS)
Tel. +31 (0)164-295149
Fax. +31 (0)164-294444
E-mail: Rottier.Pascalpmintl.ch
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com--
Roland Ottersbach
Workflow and Change Management
Parcs IT-Consulting GmbH (www.parcs.de)
Birlenbacher Strasse 14K
57078 Siegen, Germany
Phone 49 (0) 271 870 6421
Mobile 49 (0) 171 374 5171
Email roparcs.de -
Solution Manager as a source for Portal UME
Is it possible to to configure in EP 7, that UME source is Solman Abap clietn? We are using Solman as central CUA client too. Can one ABAP system can be user source for several ABAP?
Thank You
VladimitHi Vladimir
It is possible to use Sol Man as your User Data Source.
Also one ABAP system can act as a source for several other abap based systems.
Check this out:
http://help.sap.com/saphelp_nw2004s/helpdata/en/07/622441cd87a12be10000000a1550b0/frameset.htm
Cheers. -
Re: (forte-users) Oggetto: (forte-users) FYI: Forte 3.5Document
I'm very interested too in know when will be available this release 3.5.
Regards,
Danielk
----- Original Message -----
From: "Luca Gioppo" <Luca.Gioppocsi.it>
To: <Forte-userslists.xpedior.com>
Sent: Saturday, October 14, 2000 8:37 AM
Subject: (forte-users) Oggetto: (forte-users) FYI: Forte 3.5 Document
>
>
Does anyone know when will be available 3.5?
Things in the docs are quite promising.
Luca
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.comI went through the same process some time back. I
submitted a call to Forte and was informed that there
are hooks but they were intentionally undocumented
because Forte had plans to provide a interface to
Source Control Managers in future releases. If you
submit a call, they will send you a ZIP file
containing instructions on how to use the hooks. The
hooks have proven very useful.
--- Luca Gioppo <Luca.Gioppocsi.it> wrote:
>
>
I think that the topic is still open and alive.
In my case I have the need to integrate with PVCS
dimension.
The problem for me is that we develop both with java
and tool, and is
frustrating seeing java people smiling as tha
various tools give the chance to
integrate to various extends with source control
products.
I'm interested too in the problem, looking for a
solution since a bit, but no
satifactory solutions.
So count 2 on the problem.
Luca
"David Potts" <david.pottss1.com> il 23/11/2000
17.12.47
Per: forte-userslists.xpedior.com
cc: (ccr: Luca Gioppo/CSI/IT)
Oggetto: (forte-users) Source Control
Hello,
I'm looking how to do version control for forte
development, and have
done a search on the list archive. There are lots
of messages asking
how to do source control, but the answers all seem
to be "roll your
own". My questions are:
(1) Most of the postings seem to come from some
years ago. What is the
current state of play with source control for forte
4GL?
(2) There was some mention of "hooks". What are
these hooks?
(3) With Sun appearing on the scene, anyone got any
idea where source
control is going in future versions?
I'm very new to Forte, so sorry if this topic has
been closed.
Cheers,
Dave.
ATTACHMENT part 2 application/octet-streamname=david.potts.vcf
http://shopping.yahoo.com/ -
Filter plug-in: How to mix my RGB image with source document image properly?
Hi All,
My problem seems to be very common, but I can't find any answers in documentation.
I made Filter plug-in. It composes RGB image and mixes it with user source image in the document.
Now I load FilterRecord->
inData to byte array and recode each pixel with HostCSConvertColor function.
My code looks like that:
byte
*input = (byte*)filter_record->inData;
int
width = filter_record->inRect.right - filter_record->inRect.left;
int height = filter_record->inRect.bottom - filter_record->inRect.top;
byte
*transfer_buffer;
int size = width * height * 4;
transfer_buffer = new byte[size];
byte *output = transfer_buffer;
int
planes = CSPlanesFromMode(fpb->imageMode, 3);
int16 color[4];
for(j = 0; j < height; j++) {
for(i = 0; i < width; i++) {
for(k = 0; k < planes; k++) {
color[k] = input[i * align + k]; }
HostCSConvertColor(filter_record->colorServices, space, plugIncolorServicesRGBSpace, color); *
output = (byte)color[0]; output++; *
output = (byte)color[1]; output++; *
output = (byte)color[2]; output++; *
output = 255; output++; }
// for width
input += line;
} // for height
After that I mix my RGB image with output buffer and make back transition via
HostCSConvertColor to the document Color Space.It works very slow and looks ugly.
But I can't find any other way to mix my RGB image with photoshop image which can be not RGB Color Mode.
Your help will be very appreciated.
SofiaIs it important to you to be able to process input color spaces other than RGB?
You can limit your filter to accept only RGB data if you set things up properly in the PiPL resource (e.g., yourfiltername.r file).
Here's an example for a filter that accepts only RGB or grayscale images:
SupportedModes
noBitmap,
doesSupportGrayScale,
noIndexedColor,
doesSupportRGBColor,
noCMYKColor,
noHSLColor,
noHSBColor,
noMultichannel,
noDuotone,
noLABColor
EnableInfo { "in (PSHOP_ImageMode, RGBMode, GrayScaleMode, RGB48Mode, Gray16Mode, RGB96Mode, Gray32Mode)" },
With the above, the filter will be disabled (grayed-out in the menu) for modes other than those listed.
-Noel
Maybe you are looking for
-
So I have created a template with one editable region I have created a new page from template and wish to change the styling in the editable region for the new page but not the main page. When i create a new css rule it alters the main page as well,
-
trying to change my email address on my account, where do i do this?
-
I can't find Bluetooth in settings/general
I want to add a bluetooth keyboard, and it's instructions direct me to Settings/General/Bluetooth to turn it on. I have an Ipad 4th generation, but there is no Bluetooth listed at Settings/General. What am I doing wrong?
-
What is the maximum ram I can instal on the 24" iMac 2.16 GHz Intel Core 2 Duo?
-
I am working with office 2013. I was able to open the .xml files in office 2010, it opened in IE 9 just fine. Now I am using 2013, IE 11... How can I view the .xml files?