Bonjour Login vs IP Login (command-k)

Our file server is 10.4.3 w/ 2GB RAM. Our clients are all G5s running 10.4.3.
I'm wondering if something is up w/ out network config. We are a small subnet on a large corp network, and lately (since 10.4.3) I have noticed a new issue, though it has been easy to work around.
Clients on the main network crash when they attemp to connect via Binjour browsing (Via the Network area of the Finder windows) but connect fine via Command-K and the IP address.
We have a second private network, (the metadata network for our Xsan) that only 2 machines use, and on this network Bojour works fine, in fact our transfer speeds are about 30% higher when we connect via Bonjour vs IP...
I'd love to get that 30% boost for my other clients, so I'm wondering if anybody has any suggestions on network configs for getting Bonjour to behave. I think it has soemthing to do w/ DNS, as previously we have seen some DNS/Bonjour related freak outs involving the mDNSresponder process when the servers have lost access tot he main corp DNS...
any ideas???

Bonjour use IP too. Depending on your setup, subnets and such, you either have a DHCP server or use static IPs for the Xsan. I guess it might work having self assigned IP's (like 169.xxx.xxx.xxx) but I would use "real" IP's.
Bonjour use multicasts to find/present nodes/services on your LANs but if you use something like fileserver.local to mount an AFP server volume it still use TCP port 548 for that traffic.
I guess you could have some routing problems, re-using the same network numbers on more than one subnet, overlapping netmasks or some other network related problem.
That 30% speed increase must be from mounting the Xsan volume directly via FibreChannel on those computers since the metadata network only transports metadata (filelocking and such) not the actual data.
And Apple doesn't support IP over FibreChannel (yet?) so a Xsan volume is either mounted directly as a shared disc (mounting the same disc on 2 or more computers as a local volume but using the "Xsan" filesystem) or as a re-shared volume via AFP/SMB/NFS.

Similar Messages

[Solved] "slim: failed to execute login command" after awesomewm updat

Hi,
i updated some weeks ago via pacman -Syu, where also awesome wm was updated from 3.4.* to 3.5.* so I updated my rc.lua as it is told on their wiki, but i cant login with my rc.lua anymore i got the failed to execute login command error from slime. If i use the shipped efault rc.lua it works fine, can someone help me to figure out whats wrong with my rc.lua?
-- Standard awesome library
local gears = require("gears")
local awful = require("awful")
awful.rules = require("awful.rules")
require("awful.autofocus")
-- Widget and layout library
local wibox = require("wibox")
-- Theme handling library
local beautiful = require("beautiful")
-- Notification library
local naughty = require("naughty")
local menubar = require("menubar")
local vicious = require("vicious")
function fullscreens(c)
awful.client.floating.toggle(c)
if awful.client.floating.get(c) then
local clientX = screen[1].workarea.x
local clientY = screen[1].workarea.y
local clientWidth = 0
-- look at http://www.rpm.org/api/4.4.2.2/llimits_8h-source.html
local clientHeight = 2147483640
for s = 1, screen.count() do
clientHeight = math.min(clientHeight, screen[s].workarea.height)
clientWidth = clientWidth + screen[s].workarea.width
end
local t = c:geometry({x = clientX, y = clientY, width = clientWidth, height = clientHeight})
else
--apply the rules to this client so he can return to the right tag if there is a rule for that.
awful.rules.apply(c)
end
-- focus our client
client.focus = c
end
-- {{{ Error handling
-- Check if awesome encountered an error during startup and fell back to
-- another config (This code will only ever execute for the fallback config)
if awesome.startup_errors then
naughty.notify({ preset = naughty.config.presets.critical,
title = "Oops, there were errors during startup!",
text = awesome.startup_errors })
end
-- Handle runtime errors after startup
do
local in_error = false
awesome.connect_signal("debug::error", function (err)
-- Make sure we don't go into an endless error loop
if in_error then return end
in_error = true
naughty.notify({ preset = naughty.config.presets.critical,
title = "Oops, an error happened!",
text = err })
in_error = false
end)
end
-- {{{ Variable definitions
-- Themes define colours, icons, and wallpapers
-- beautiful.init("/home/kili/Repositories/awesome-themes/arch/theme.lua")
beautiful.init("/usr/share/awesome/themes/default/theme.lua")
-- This is used later as the default terminal and editor to run.
terminal = "urxvt"
editor = os.getenv("EDITOR") or "nano"
editor_cmd = terminal .. " -e " .. editor
-- Default modkey.
-- Usually, Mod4 is the key with a logo between Control and Alt.
-- If you do not like this or do not have such a key,
-- I suggest you to remap Mod4 to another key using xmodmap or other tools.
-- However, you can use another modifier like Mod1, but it may interact with others.
modkey = "Mod4"
-- Table of layouts to cover with awful.layout.inc, order matters.
layouts =
awful.layout.suit.tile,
awful.layout.suit.tile.left,
awful.layout.suit.tile.bottom,
awful.layout.suit.tile.top,
awful.layout.suit.floating,
awful.layout.suit.fair,
awful.layout.suit.fair.horizontal,
awful.layout.suit.spiral,
awful.layout.suit.spiral.dwindle,
awful.layout.suit.max,
awful.layout.suit.max.fullscreen,
awful.layout.suit.magnifier
-- {{{ Tags
-- Define a tag table which hold all screen tags.
tags = {}
for s = 1, screen.count() do
-- Each screen has its own tag table.
tags[s] = awful.tag({ 1, 2, 3, 4, 5}, s, layouts[1])
end
-- {{{ Menu
-- Create a laucher widget and a main menu
myawesomemenu = {
{ "manual", terminal .. " -e man awesome" },
{ "edit config", editor_cmd .. " " .. awesome.conffile },
{ "restart", awesome.restart },
{ "quit", awesome.quit }
mymainmenu = awful.menu({ items = { { "awesome", myawesomemenu, beautiful.awesome_icon },
{ "open terminal", terminal }
mylauncher = awful.widget.launcher({ image = beautiful.awesome_icon, menu = mymainmenu })
-- {{{ Wibox
-- Create a textclock widget
batwidget = wibox.widget.textbox()
vicious.register(batwidget, vicious.widgets.bat,
function(widget,args)
local formatstring = " Bat: "..args[1]..args[2] .."%".. " "..args[3] .. " "
if args[2] <= 25 and args[1] == "-" then
return "".. formatstring .. ""
end
return formatstring
end, 60, "BAT0")
netwidgetETH = wibox.widget.textbox()
netwidgetWIFI = wibox.widget.textbox()
vicious.register(netwidgetETH, vicious.widgets.net, ' eth0:${eth0 down_kb} ${eth0 up_kb}', 3)
vicious.register(netwidgetWIFI, vicious.widgets.net,' wlan0:${wlan0 down_kb} ${wlan0 up_kb}', 3)
menubar.utils.terminal = terminal
mytextclock = awful.widget.textclock()--{ align = "right" })
-- Create a systray
mysystray = wibox.widget.systray()
-- Create a wibox for each screen and add it
mywibox = {}
mypromptbox = {}
mylayoutbox = {}
mytaglist = {}
mytaglist.buttons = awful.util.table.join(
awful.button({ }, 1, awful.tag.viewonly),
awful.button({ modkey }, 1, awful.client.movetotag),
awful.button({ }, 3, awful.tag.viewtoggle),
awful.button({ modkey }, 3, awful.client.toggletag),
awful.button({ }, 4, function(t) awful.tag.viewnext(aweful.tag.getscreen(t)) end),
awful.button({ }, 5, function(t) awful.tag.viewprev(aweful.tag.getscreen(t)) end)
mytasklist = {}
mytasklist.buttons = awful.util.table.join(
awful.button({ }, 1, function (c)
if c == client.focus then
c.minimized = true
else
c.minimized = false
if not c:isvisible() then
awful.tag.viewonly(c:tags()[1])
end
-- This will also un-minimize
-- the client, if needed
client.focus = c
c:raise()
end
end),
awful.button({ }, 3, function ()
if instance then
instance:hide()
instance = nil
else
instance = awful.menu.clients({ width=250 })
end
end),
awful.button({ }, 4, function ()
awful.client.focus.byidx(1)
if client.focus then client.focus:raise() end
end),
awful.button({ }, 5, function ()
awful.client.focus.byidx(-1)
if client.focus then client.focus:raise() end
end))
for s = 1, screen.count() do
-- Create a promptbox for each screen
mypromptbox[s] = awful.widget.prompt()--{ layout = awful.widget.layout.horizontal.leftright })
-- Create an imagebox widget which will contains an icon indicating which layout we're using.
-- We need one layoutbox per screen.
mylayoutbox[s] = awful.widget.layoutbox(s)
mylayoutbox[s]:buttons(awful.util.table.join(
awful.button({ }, 1, function () awful.layout.inc(layouts, 1) end),
awful.button({ }, 3, function () awful.layout.inc(layouts, -1) end),
awful.button({ }, 4, function () awful.layout.inc(layouts, 1) end),
awful.button({ }, 5, function () awful.layout.inc(layouts, -1) end)))
-- Create a taglist widget
mytaglist[s] = awful.widget.taglist(s, awful.widget.taglist.filter.all, mytaglist.buttons)
-- Create a tasklist widget
mytasklist[s] = awful.widget.tasklist(s, awful.widget.tasklist.filter.currenttags, mytasklist.buttons)
-- Create the wibox
mywibox[s] = awful.wibox({ position = "top", screen = s })
-- Widgets that are aligned to the left
local left_layout = wibox.layout.fixed.horizontal()
left_layout:add(mylauncher)
left_layout:add(mytaglist[s])
left_layout:add(mypromptbox[s])
-- Widgets that are aligned to the right
local right_layout = wibox.layout.fixed.horizontal()
if s == 1 then right_layout:add(wibox.widget.systray()) end
right_layout:add(netwidgetWIFI)
right_layout:add(netwidgetETH)
right_layout:add(batwidget)
right_layout:add(mytextclock)
right_layout:add(mylayoutbox[s])
-- Now bring it all together (with the tasklist in the middle)
local layout = wibox.layout.align.horizontal()
layout:set_left(left_layout)
layout:set_middle(mytasklist[s])
layout:set_right(right_layout)
mywibox[s]:set_widget(layout)
-- Add widgets to the wibox - order matters
--mywibox[s].widgets = {
-- mylauncher,
-- mytaglist[s],
-- mypromptbox[s],
--layout = awful.widget.layout.horizontal.leftright
-- mylayoutbox[s],
-- mytextclock,
-- batwidget,
-- netwidgetETH,
-- netwidgetWIFI,
-- s == 1 and mysystray or nil,
-- mytasklist[s],
-- layout = awful.widget.layout.horizontal.rightleft
end
-- {{{ Mouse bindings
root.buttons(awful.util.table.join(
awful.button({ }, 3, function () mymainmenu:toggle() end),
awful.button({ }, 4, awful.tag.viewnext),
awful.button({ }, 5, awful.tag.viewprev)
-- {{{ Key bindings
globalkeys = awful.util.table.join(
awful.key({ modkey, }, "Left", awful.tag.viewprev ),
awful.key({ modkey, }, "Right", awful.tag.viewnext ),
awful.key({ modkey, }, "Escape", awful.tag.history.restore),
awful.key({ modkey, }, "j",
function ()
awful.client.focus.byidx( 1)
if client.focus then client.focus:raise() end
end),
awful.key({ modkey, }, "k",
function ()
awful.client.focus.byidx(-1)
if client.focus then client.focus:raise() end
end),
awful.key({ modkey, }, "w", function () mymainmenu:show() end),
-- Layout manipulation
awful.key({ modkey, "Shift" }, "j", function () awful.client.swap.byidx( 1) end),
awful.key({ modkey, "Shift" }, "k", function () awful.client.swap.byidx( -1) end),
awful.key({ modkey, "Control" }, "j", function () awful.screen.focus_relative( 1) end),
awful.key({ modkey, "Control" }, "k", function () awful.screen.focus_relative(-1) end),
awful.key({ modkey, }, "u", awful.client.urgent.jumpto),
awful.key({ modkey, }, "Tab",
function ()
awful.client.focus.history.previous()
if client.focus then
client.focus:raise()
end
end),
-- Standard program
awful.key({ modkey, }, "Return", function () awful.util.spawn(terminal) end),
awful.key({ modkey, "Control" }, "r", awesome.restart),
awful.key({ modkey, "Shift" }, "q", awesome.quit),
awful.key({ modkey, }, "l", function () awful.tag.incmwfact( 0.05) end),
awful.key({ modkey, }, "h", function () awful.tag.incmwfact(-0.05) end),
awful.key({ modkey, "Shift" }, "h", function () awful.tag.incnmaster( 1) end),
awful.key({ modkey, "Shift" }, "l", function () awful.tag.incnmaster(-1) end),
awful.key({ modkey, "Control" }, "h", function () awful.tag.incncol( 1) end),
awful.key({ modkey, "Control" }, "l", function () awful.tag.incncol(-1) end),
awful.key({ modkey, }, "space", function () awful.layout.inc(layouts, 1) end),
awful.key({ modkey, "Shift" }, "space", function () awful.layout.inc(layouts, -1) end),
awful.key({ modkey, "Control" }, "n", awful.client.restore),
-- Prompt
awful.key({ modkey }, "r", function () mypromptbox[mouse.screen]:run() end),
awful.key({ modkey }, "x",
function ()
awful.prompt.run({ prompt = "Run Lua code: " },
mypromptbox[mouse.screen].widget,
awful.util.eval, nil,
awful.util.getdir("cache") .. "/history_eval")
end),
-- Multimedia
awful.key({ }, "XF86AudioLowerVolume", function () awful.util.spawn("amixer -q sset Master 2dB-") end),
awful.key({ }, "XF86AudioRaiseVolume", function () awful.util.spawn("amixer -q sset Master 2dB+") end),
awful.key({ }, "XF86AudioNext",function () awful.util.spawn( "mocp -f" ) end),
awful.key({ }, "XF86AudioPrev",function () awful.util.spawn( "mocp -r" ) end),
awful.key({ }, "XF86AudioPlay",function () awful.util.spawn( "mocp -G" ) end),
awful.key({ }, "Print", function () awful.util.spawn("ksnapshot") end),
awful.key({ }, "", function () awful.util.spawn("slimlock") end)
clientkeys = awful.util.table.join(
awful.key({ modkey, }, "f", function (c) c.fullscreen = not c.fullscreen end),
awful.key({ modkey, "Shift" }, "c", function (c) c:kill() end),
awful.key({ modkey, "Control" }, "space", awful.client.floating.toggle ),
awful.key({ modkey, "Control" }, "Return", function (c) c:swap(awful.client.getmaster()) end),
awful.key({ modkey, }, "o", awful.client.movetoscreen ),
-- awful.key({ modkey, "Shift" }, "r", function (c) c:redraw() end),
awful.key({ modkey, }, "t", function (c) c.ontop = not c.ontop end),
awful.key({ modkey, }, "n",
function (c)
-- The client currently has the input focus, so it cannot be
-- minimized, since minimized clients can't have the focus.
c.minimized = true
end),
awful.key({ modkey, }, "m",
function (c)
c.maximized_horizontal = not c.maximized_horizontal
c.maximized_vertical = not c.maximized_vertical
end),
awful.key({ modkey, "Shift" }, "f", fullscreens)
-- Compute the maximum number of digit we need, limited to 9
keynumber = 0
for s = 1, screen.count() do
keynumber = math.min(9, math.max(#tags[s], keynumber))
end
-- Bind all key numbers to tags.
-- Be careful: we use keycodes to make it works on any keyboard layout.
-- This should map on the top row of your keyboard, usually 1 to 9.
for i = 1, keynumber do
globalkeys = awful.util.table.join(globalkeys,
awful.key({ modkey }, "#" .. i + 9,
function ()
local screen = mouse.screen
if tags[screen][i] then
awful.tag.viewonly(tags[screen][i])
end
end),
awful.key({ modkey, "Control" }, "#" .. i + 9,
function ()
local screen = mouse.screen
if tags[screen][i] then
awful.tag.viewtoggle(tags[screen][i])
end
end),
awful.key({ modkey, "Shift" }, "#" .. i + 9,
function ()
if client.focus and tags[client.focus.screen][i] then
awful.client.movetotag(tags[client.focus.screen][i])
end
end),
awful.key({ modkey, "Control", "Shift" }, "#" .. i + 9,
function ()
if client.focus and tags[client.focus.screen][i] then
awful.client.toggletag(tags[client.focus.screen][i])
end
end))
end
clientbuttons = awful.util.table.join(
awful.button({ }, 1, function (c) client.focus = c; c:raise() end),
awful.button({ modkey }, 1, awful.mouse.client.move),
awful.button({ modkey }, 3, awful.mouse.client.resize))
-- Set keys
root.keys(globalkeys)
-- Set Firefox to always map on tags number 2 of screen 1.
-- { rule = { class = "Firefox" },
-- properties = { tag = tags[1][2] } },
-- {{{ Rules
if screen.count() > 1 then
awful.rules.rules = {
-- All clients will match this rule.
{ rule = { },
properties = { border_width = beautiful.border_width,
-- border_color = beautiful.border_normal,
focus = true,
keys = clientkeys,
buttons = clientbuttons } },
{ rule = { class = "MPlayer" },
properties = { floating = true } },
{ rule = { class = "gimp" },
properties = { floating = true } },
{ rule = { class = "Xdialog" },
properties = { floating = true } },
{ rule = { class = "Firefox" },
properties = { tag = tags[1][1] } },
{ rule = { name = "Thunderbird" },
properties = { tag = tags[1][2] } },
{ rule = { instance = "plugin-container" },
properties = { floating = true } },
{ rule = { class = "Luakit" },
properties = { floating = true } }
else
awful.rules.rules = {
-- All clients will match this rule.
{ rule = { },
properties = { border_width = beautiful.border_width,
-- border_color = beautiful.border_normal,
focus = true,
keys = clientkeys,
buttons = clientbuttons } },
{ rule = { class = "MPlayer" },
properties = { floating = true } },
{ rule = { class = "gimp" },
properties = { floating = true } },
{ rule = { class = "Firefox" },
properties = { tag = tags[1][2] } },
{ rule = { name = "Thunderbird" },
properties = { tag = tags[1][3] } },
{ rule = { instance = "plugin-container" },
properties = { floating = true, fullscreen = true } },
{ rule = { class = "Dolphin" },
properties = { floating = false, fullscreen = false, tag = tags[1][4] } },
{ rule = { class = "Luakit" },
properties = { floating = true } },
{ rule = { class = "Pidgin" },
properties = { tag = tags[1][5] } }
end
-- {{{ Signals
-- Signal function to execute when a new client appears.
client.connect_signal("manage", function (c, startup)
-- Add a titlebar
-- awful.titlebar.add(c, { modkey = modkey })
-- Enable sloppy focus
c:connect_signal("mouse::enter", function(c)
if awful.layout.get(c.screen) ~= awful.layout.suit.magnifier
and awful.client.focus.filter(c) then
client.focus = c
end
end)
if not startup then
-- Set the windows at the slave,
-- i.e. put it at the end of others instead of setting it master.
-- awful.client.setslave(c)
-- Put windows in a smart way, only if they does not set an initial position.
if not c.size_hints.user_position and not c.size_hints.program_position then
awful.placement.no_overlap(c)
awful.placement.no_offscreen(c)
end
end
local titlebars_enabled = false
if titlebars_enabled and (c.type == "normal" or c.type == "dialog") then
-- Widgets that are aligned to the left
local left_layout = wibox.layout.fixed.horizontal()
left_layout:add(awful.titlebar.widget.iconwidget(c))
-- Widgets that are aligned to the right
local right_layout = wibox.layout.fixed.horizontal()
right_layout:add(awful.titlebar.widget.floatingbutton(c))
right_layout:add(awful.titlebar.widget.maximizedbutton(c))
right_layout:add(awful.titlebar.widget.stickybutton(c))
right_layout:add(awful.titlebar.widget.ontopbutton(c))
right_layout:add(awful.titlebar.widget.closebutton(c))
-- The title goes in the middle
local title = awful.titlebar.widget.titlewidget(c)
title:buttons(awful.util.table.join(
awful.button({ }, 1, function()
client.focus = c
c:raise()
awful.mouse.client.move(c)
end),
awful.button({ }, 3, function()
client.focus = c
c:raise()
awful.mouse.client.resize(c)
end)
-- Now bring it all together
local layout = wibox.layout.align.horizontal()
layout:set_left(left_layout)
layout:set_right(right_layout)
layout:set_middle(title)
awful.titlebar(c):set_widget(layout)
end
end)
client.connect_signal("focus", function(c) c.border_color = beautiful.border_focus end)
client.connect_signal("unfocus", function(c) c.border_color = beautiful.border_normal end)
Here is also my slime config and my initrc
ls -lisa .xinitrc
3276814 4 -rwxr-xr-x ...
#!/bin/sh
xrdb -merge ~/.Xresources
wicd-client --tray &
exec awesome #>> ~/.cache/awesome/stdout 2>> ~/.cache/awesome/stderr
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path /bin:/usr/bin:/usr/local/bin
default_xserver /usr/bin/X
xserver_arguments -nolisten tcp vt07
# Commands for halt, login, etc.
halt_cmd /sbin/shutdown -h now
reboot_cmd /sbin/shutdown -r now
console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd /usr/sbin/suspend
# Full path to the xauth binary
xauth_path /usr/bin/xauth
# Xauth file for server
authfile /var/run/slim.auth
# Activate numlock when slim starts. Valid values: on|off
numlock on
# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor false
# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd exec /bin/sh - ~/.xinitrc %session
login_cmd exec /bin/bash -login ~/.xinitrc %session
# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
# sessionstart_cmd some command
# sessionstop_cmd some command
# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
# daemon yes
# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions awesome,xfce4,icewm-session,wmaker,blackbox
# Executed when pressing F11 (requires imagemagick)
screenshot_cmd import -window root /slim.png
# welcome message. Available variables: %host, %domain
welcome_msg Welcome to %host
# Session message. Prepended to the session name when pressing F1
# session_msg Session:
# shutdown / reboot messages
shutdown_msg The system is halting...
reboot_msg The system is rebooting...
# default user, leave blank or remove this line
# for avoid pre-loading the username.
default_user kili
# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
focus_password yes
# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
#auto_login no
# current theme, use comma separated list to specify a set to
# randomly choose from
current_theme archlinux-simplyblack
# Lock file
lockfile /var/lock/slim.lock
# Log file
logfile /var/log/slim.log
Thanks in advance!
Edit:
Besides a lot of other errors the problem was the systray. It was created 2 times, now login works again. I figured that out via enabling logging for awesome in the xinitrc again.
Last edited by stubb (2013-01-08 23:20:05)

Hi,
I have the same kind of issue after updated slim from v1.3.4-4 to v1.3.5-1.
see my topic here :
https://bbs.archlinux.org/viewtopic.php?id=156792
Last edited by cedricl (2013-01-24 17:16:42)

[svn] 1978: Bug: vendors. properties file which is used in vendor specific login commands was not being read properly and as a result some login related error messages were not being displayed correctly .

Revision: 1978
Author: [email protected]
Date: 2008-06-06 08:05:34 -0700 (Fri, 06 Jun 2008)
Log Message:
Bug: vendors.properties file which is used in vendor specific login commands was not being read properly and as a result some login related error messages were not being displayed correctly.
QA: Yes - we need automated tests to make sure that errors.properties and vendors.properties in BlazeDS/LCDS are loaded properly.
Doc: No
Modified Paths:
blazeds/branches/3.0.x/modules/common/src/java/flex/messaging/util/PropertyStringResource Loader.java
blazeds/branches/3.0.x/modules/opt/src/jrun/flex/messaging/security/JRunLoginCommand.java
blazeds/branches/3.0.x/modules/opt/src/tomcat/flex/messaging/security/TomcatLoginCommand. java

I have a lot of grief with this version of Windows Media Player.
It is very buggy and frustrating to use.
I have my Music library on a QNAP NAS, which is as reliable as they come.
System notifications make it not save changes. It also does not do a good job of interpreting albums and artists from folders. Changes to track names are not saved, nor are tracks moved to other albums, renamed albums, changes to genre, artist
or date. It separates and merges albums/tracks without sense or reason. Some changes I've made up to 4 times, then closed WMP and re-started my machine to check if it has/hasn't saved the changes. Often it has not.
This is the first time I've used WMP in this capacity, and I do not recommend it.
New service pack please.

No login command was found for 'WebLogic Server 10.3.5.0 - in managed serve

i am getting following warning when i run my web logic managed server
No login command was found for 'WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 Oracle WebLogic Server Module Dependencies 10.3 Thu Mar 3 14:37:52 PST 2011 Oracle WebLogic Server on JRockit Virtual Edition Module Dependencies 10.3 Thu Feb 3 1.
Would appreciate suggestions to resolve.
Thanks.

Hi,
Add -Dweblogic.StdoutDebugEnabled flag while starting the managed server and then post the verbose error message in your next post
For setting the flag follow the below steps
If your using Linux box and not using node manager to start the managed server,add the below line startManagedWebLogic.sh file
JAVA_OPTIONS="-Dweblogic.StdoutDebugEnabled=true ${JAVA_OPTIONS}"
echo "JAVA_OPTIONS=${JAVA_OPTIONS}"
If your using Windows box and not using node manager to start the managed server,add the below line startManagedWebLogic.cmd file
set JAVA_OPTIONS=-Dweblogic.StdoutDebugEnabled=true %JAVA_OPTIONS%
echo JAVA_OPTIONS=%JAVA_OPTIONS%
If you are starting the Managed server through the node manager then use these flags From Admin console : servers >>>. MS1 >>>> server start >>>> Arguments :-Dweblogic.StdoutDebugEnabled=true
Regards,
Fabian

What is Login command in VTY configuration

Pls information in usage of Login command in VTY configuration in brief

Hi,
Login is used to control VTY access, it generally has 4 cases when AAA is not configured, and with AAA it serves another purpose:
Without AAA:
One of the following methods must be explicitly configure otherwise there can't be VTY access to the router.
1. "no login" > No password is required for VTY access
2. "login" + "password xxxx" > This password is required for login.
3. "login local" + "username xxxx password xxxx" (global configuration) > a local configured username and password are required for login.
4. "login tacacs" + "tacacs-server host x.x.x.x" (global configuration) > Use TACACS or Extended TACACS server for login.
With AAA:
With AAA it can be used to specify a custom AAA authentication method using the "login authentication xxxx" command under the VTYs.
NOTE TACACS+ can be enabled only through AAA commands.
I hope that i've been informative.
BR,
Mohammed Mahmoud.

SQLException when execute CREATE LOGIN Command

Dear Friends,
I have connected the MSSQL Server Database through java program using the following connection code.
String loginName = "login1";
String password = "pass1";
String connectionString = "jdbc:sqlserver://C-1120\\SQLEXPRESS:1433;databaseName=TESTDB2;applicationName=SQLConnectionExpress;"
DriverManager.registerDriver (new com.microsoft.sqlserver.jdbc.SQLServerDriver());
conn = DriverManager.getConnection(connectionString, userName,pass);
String selectQry = "CREATE LOGIN TEST_LOGIN1 WITH PASSWORD = 'PASSWORD1'";
stmt = conn.createStatement();
stmt.execute(selectQry);When i execute the above program, i got following SQLExpection,
com.microsoft.sqlserver.jdbc.SQLServerException: User does not have permission to perform this action.
If i execute the same command (CREATE LOGIN) using the above loginName (login1) in MS SQL Server, it executes fine.
But if i execute through program I got an above exception.
Could any one pls help me to solve this issue?
Thanks in advance...

i got it. Hade to put security off in enterprise manager.

Unix Login Command

Anyone know how to login multiple machines at once? I've heard there's a UNIX command you can send, anyone know it? It'd be nice if I could login all of the machines in one shot, instead of going one at a time!

Try this link
http://www.macosxhints.com/article.php?story=2005062918513721
It should help.
-- Tim

"start" not called for Custom Login Command

Hello,
I'm working on getting acegi to handle the authentication instead of the app server. So I extended AppServerLoginCommand and overrode doAuthenticate and "start". But "start" never seems to get called; neither during initialization of the server nor before or after doAuthenticate is called. Note that doAuthenticate *does* get called, so BlazeDS does know about my custom command. I tried implementing just LoginCommand instead of extending AppServerLoginCommand but the same result.
The reason I need start is because I want to grab the WebApplicationContext and from there get the authenticationManager bean so that doAuthentication can do its job.
I noticed that "stop" never gets called either.
Any pointers or clues would be appreciated.
/r

I looked through the source code and as best I can tell "start" never gets called for LoginCommand. This is, by no means, a certainty since I only partially followed the stack trace and looked at the source near the place where the LoginCommand gets created, so there may be another point in the lifecycle where start gets called. But anyway, if you look at the file at:
http://opensource.adobe.com/svn/opensource/blazeds/trunk/modules/core/src/java/flex/messag ing/config/MessagingConfiguration.java
near
private LoginCommand initLoginCommand(LoginCommandSettings loginCommandSettings)
you'll notice that the LoginCommand gets created but start is not called.

Running commands on GNOME login/logout

Hi everyone,
I have a truecrypt partition which I want to mount on GNOME login and dismount on logout. My approach is different to the one in the Truecrypt wiki since I don't like having passwords stored unencrypted in files:
What I want to do is basically run "sudo truecrypt --auto-mount=favorites" everytime my user logs in to GNOME (not to a terminal) and run "sudo truecrypt -d" on logout.
How can I do this? I didn't find anything in the GNOME wiki entry or on the web, only for logins in general using .bashrc which is not what I want.
Thanks for any help.
BTW, does anyone know why there is no possibility to start TrueCrypt minimized to tray (the TrueCrypt Background Task) on Linux? Also, the Windows version has a "Mount favorite volumes on startup" setting which I couldn't find in the Linux version. These two things would have saved me a lot of time.

arkham wrote:If you are using gdm to login/logout you could take a look in /etc/gdm. There are some folders called PreSession and PostSession which may be useful to you,
Somehow these folders don't work for me. I decided to use the GNOME startup programs to run the mount command since it shows a window requesting the volume password. I added a "Truecrypt" file with the following content to the PostSession folder, made it executable by everyone, but my volume doesn't get unmounted.
#!/bin/sh
sudo truecrypt -d
exit 0
The solution for the login command is basically found, any suggestions how to get the PostSession file working or even another way to run the logout command?

Please help! Bizarre login/user account problem

In 24 years of using Macs, this is the most frustrating thing I've ever faced and I am in desperate need of help.
For the entire story of my circumstances, see below. The short version of my problem: My auto-login user account is corrupt but I can't figure out how to bypass/interrupt it so I can log in to a different user account. Is there a way to use Single User Mode to do this - to get to the regular login screen where I can enter a different user name and password???
I follwed the steps outlined by Michael in this thread, but it did not work
http://discussions.apple.com/thread.jspa?threadID=1124380
Any expedient help is greatly appreciated, I'm in dire straights...my Mac has been down for a week with this problem and my work is suffering.
Thanks in advance,
-Nelson
Here's the long version of how I arrived at these circumstances:
I have a single (admin level) user account on my new Mac Pro, with auto-login enabled. The home folder is on a separate internal drive (bay 2) from the OS/applications (bay 1). Out of nowhere, I got the error "You are unable to log in to the user account. Login failed because an error occurred." I was not able to login to my machine. When I tried to boot from my bootable clone backup, got the same error. Tried to boot from the Leopard install DVD, got the 5-language kernel panic screen. Off to the Apple Store.
It didn't occur to me at this time to mention my Home folder being on a 2nd drive, that was my mistake #1. They ended up replacing the logic board and RAM riser cards, neither of which was remotely related to the problem. In the process, they were able to create a new admin-level 'test' user account, and got the machine up and running again. At this point they noticed that there was no other user/Home folder present on the startup drive and at this point I told them that it was located on drive 2. That drive was not appearing in the finder, so apparently it had croaked - and knowing this pretty much explained the original problem, to me at least.
I get home, log in as Test, delete my old user account, create a new user account and put the Home folder for this new account on drive 3. My stupid mistake #2: I used the same name for the new account as my old account, and mistake #3, turned auto-login to this account back on.
But at this point, everything was still working, and I commenced to try to recover my lost Home folder from my Time Machine backup and figure out how to restore all of my system settings, which were wiped out with the creation of the new Test user account. I'll skip over some of the other problems I ran into with Time Machine at this point and get to the real issue: after a couple of successful restarts and logins to my newly created user account (the one with the same name as my old account but with it's Home folder in a different location), the ORIGINAL "You are unable to log in to the user account. Login failed because an error occurred." error has returned.
Now I'm back where I started, and can't figure out how to log in to the Test account that resides on my startup drive, because auto-login is enabled for the 'broken' user account - even though the Home folder for this account is located on a working drive.
I've done tons of searching and can't figure out how to use Single User Mode to login to Test. When I try the login command, it says 'login incorrect', even though I am using the correct user and password. Help!!

well, something is really messed up with those accounts so I would create a new admin account, log into that and go from there.
To do that [enable the root user|http://support.apple.com/kb/TS1278], safe boot, log in as root and create a new admin account, also while you are at it disable the auto login.
You can also work from the root account but I would recommend against it. It's not really safe.

Getting fault while Login.

Eclipse 3.2.2\
MyEclipse 5.5.1
JBoss 4.0.1
Flex 3.0(Beta 3.0 plugin)
Flex 3.0 compiler(having WEB-INF/flex internal.)
Hi,
I have deployed .war with JBoss after successful removing all
warnings for "using deprecated APIs for resourceBundle.getString"
replaced with ResourceManager.getInstance().getString().
Now, I am facing one problem:
TypeError: Error #1009: Cannot access a property or method of
a null object reference.
at AppName/fault()
at com.AppName.client.login.commands::LoginCommand/fault()
at mx.rpc::AsyncToken/
http://www.adobe.com/2006/flex/mx/internal::applyFault()
at mx.rpc.events::FaultEvent/
http://www.adobe.com/2006/flex/mx/internal::callTokenResponders()
at mx.rpc::AbstractOperation/
http://www.adobe.com/2006/flex/mx/internal::dispatchRpcEvent()
at mx.rpc::AbstractInvoker/
http://www.adobe.com/2006/flex/mx/internal::faultHandler()
at mx.rpc::Responder/fault()
at mx.rpc::AsyncRequest/fault()
at mx.messaging::ChannelSet/faultPendingSends()
at mx.messaging::ChannelSet/channelFaultHandler()
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at mx.messaging::Channel/connectFailed()
at mx.messaging.channels::PollingChannel/connectFailed()
at mx.messaging.channels::AMFChannel/statusHandler()
Can anyone suggest any solution for this ???
Thanks,
Prashant D Shelke.

Problem mention in first point is resolved by adding following
node:
<servlet>
<servlet-name>MessageBrokerServlet</servlet-name>
<display-name>MessageBrokerServlet</display-name>
<servlet-class>flex.messaging.MessageBrokerServlet</servlet-class>
<init-param>
<param-name>services.configuration.file</param-name>
<param-value>/WEB-INF/flex/services-config.xml</param-value>
</init-param>
<init-param>
<param-name>flex.write.path</param-name>
<param-value>/WEB-INF/flex</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
But now facing problem like:
18:25:01,828 INFO [STDOUT] 2008-02-19 18:25:01,828 ERROR
org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/smartLMS]
- StandardWrapper.Throwable
flex.messaging.config.ConfigurationException: Attribute
'per-client-authentication' must be specified for element
'login-command'.
at
flex.messaging.config.AbstractConfigurationParser.requiredAttributesOrElements(AbstractCo nfigurationParser.java:329)
at
flex.messaging.config.ServerConfigurationParser.securitySection(ServerConfigurationParser .java:133)
at
flex.messaging.config.ServerConfigurationParser.parseTopLevelConfig(ServerConfigurationPa rser.java:53)
at
flex.messaging.config.AbstractConfigurationParser.parse(AbstractConfigurationParser.java: 68)
at
flex.messaging.config.ConfigurationManager.getMessagingConfiguration(ConfigurationManager .java:77)
at
flex.messaging.MessageBrokerServlet.init(MessageBrokerServlet.java:90)
While start-up of JBoss 4.0.1
Is there any additional setting is thr ???
Please help.
Thanks,
Prashant D Shelke.

Slim: want login root to console and user to xfce

Just got Arch installed and running for the first time a couple of days ago.
I got slim to log in to user and launch xfce ok.
I cannot seem to get slim to start a console on the same laptop. If I type console in slim it doesn't accept that. It will log in as root to xfce if I have that in root's .xinitrc, but I cannot seem to log in as root to console.

I more of less got this working like I want now. Instead of using console for login, I use root. I have the following for my .xinitrc file in root.
#!/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
# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
exec xterm -geometry 227x59 -fg white -bg black
I have the login command for slim in /etc/slim.conf to be: login_cmd exec /bin/bash -login ~/.xinitrc %session
With this setup I can log in as user, but not console.
If I use the login command for slim in /etc/slim.conf: login_cmd exec /bin/sh /etc/X11/Xsession
I can login as console but not as a user straight to xfce4.
EDIT: Edited -geometry setting as it was extending beyond the deskop. Got previous setting from another forum post.
Last edited by David Batson (2011-10-18 20:33:31)

Desktop Login Problem

I am having a login issue. I am only able to login as root with the desktop login. All users can login command line.
No idea what I am missing in the user profiles. Could permissions cause this?

Hello, is this still happening? I cannot reproduce on my end.
Sami

LDAPv3 Authentication at Login Window in Leopard (10.5.2)

Hi. I'm having a problem with LDAP authentication in Leopard (10.5.2). I'm using an identical configuration to my Tiger set up, but it simply fails at Login Window. So far, I've done the following:
1) Changed the TLS_REQCERT entry in '/etc/openldap/ldap.conf' to never.
2) Tried to browse the directory using 'dscl'. I can browse to localhost->LDAPv3->server.domain->Users->my user... so it seems as though the directory is set up fine.
3) Tried logging in using 'login' in terminal. If i use that command, and log in using my LDAP credentials, I can authenticate just fine.
I also decided to run the 'id' command on a domain user and, as expected, it worked. An example would be:
dev-mac01:~ cssd$ id blp25
uid=502(BLP25) gid=20(staff) groups=20(staff),98(lpadmin),81(_appserveradm),101(com.apple.sharepoint.group.1),102(com.apple.share point.group.2),79(appserverusr),80(admin)
Finally, I just deleted the /Library/Preferences/DirectoryService directory. Rebooted. Recreated the config. Rebooted. I can log in using the login command in terminal just as before, but I cannot log in at Login Window (it shakes its window at me). The option in the Accounts System Preferences panel to allow network account logins is CHECKED.
Any help is much appreciated.

I'm not using AD binding. I'm using the LDAPv3 plug-in. I choose to do it this way, partially because I can do more specific mapping between domain attributes and local attribtues, and partially because I don't want to have each computer have a computer account in the domain.
What the 'id' output is showing is that I'm able to search for a domain user (with no actual account on the local machine). In the LDAP plugin, the UniqueID and PrimaryGroupID attributes are mapped to local ones (for the sake of making the network user appear as a specific local user).. specifically UID 502 (represented as #502 in the configuration) and GID 20 (represented as #20 in the configuration).
As I said, this identical configuration worked perfectly in 10.4.x and 10.3.x.. but does not work in 10.5.x. If I DO use AD binding, everything works as expected, but it introduces other issues I don't want to deal with. Thanks for the reply.
UPDATE: One final note.. there are only two local accounts on the computer... so none of the domain users I'd be attempting to authenticate as would conflict. On and one more final note (because having multiple final notes is fun), the actual authentication mechanism is clearly working since I can use 'login' to authenticate. LoginWindow seems simply not willing to authenticate against LDAP as 'login' is.
Message was edited by: brandonlp

Agetty's problem? or login's problem?(solved)

Hello all!!
I don't know what happened, I couldn't not login in the virtual console... Everytime i input my username, it will skip the password input step and show me some information about login this command itself. I guess there is a problem with my agetty or login file.
I tried login command: sudo login -p zhe
but it doesn't work, the output is only this
Usage: login [-p] [name]
login [-p] [-h host] [-f name]
login [-p] -r host
So I guess my login file has some problem?
Thanks everyone!
Last edited by linuxcity (2008-09-22 13:50:59)

copying the login file from directory bin in the installation CD solved the problem, but still it is really odd....

Bonjour Login vs IP Login (command-k)

Similar Messages

Maybe you are looking for