From: DMack@Tickets.com (Mack, Daemian)
Subject: [sup-talk] startup crash
Date: Mon, 10 Mar 2008 10:01:14 -0400 [thread overview]
Message-ID: <61B99676296C5044A1A088C0D0EA1BA801B3C342@syr2k3mail> (raw)
In-Reply-To: <20080310134823.GA24401@lenin>
> > But I'm still curious, why this dependency problem is showing itself
> > in a such odd way ?
>
> Not sure. Sup generates the default name value using:
>
> require 'etc'
> Etc.getpwnam(ENV["USER"]).gecos.split(/,/).first
>
> What does that evaluate to on your system?
>
> Now that actually could evaluate to nil for a variety of
> reasons, so I've fixed the logic to avoid the crash if so.
> But I'm not sure why it would be nil due to iconv not being installed.
I was getting the 'no name for account' message recently too, when
setting up a test sup instance to play with the indexing, and wondered
if it might be related to gecos info.
I've tried the test snippet above on three boxes (Debian Etch, Debian
Sarge, Ubuntu 7.10), and it returns the current username when run under
an existing user account. If I add a test user, and run the snippet as
that user, it returns nil. This is true for all three boxes. I
eventually got around it by hardcoding a dummy account name in
account.rb, as I haven't had time to Do The Right Thing and figure out
why ENV["USER"] isn't getting set for new accounts.
Thanks for sup, incidentally! I'm experimenting with using it to manage
a huge influx of business emails that Outlook makes somewhat annoying.
DJFM
--
Daemian Mack
Configuration Management
Tickets.com
344 W Genesee St
Syracuse NY, 13202
315.479.6663 x476
AIM: daemianmack
next parent reply other threads:[~2008-03-10 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080310134823.GA24401@lenin>
2008-03-10 14:01 ` Mack, Daemian [this message]
2008-03-10 17:12 ` William Morgan
2008-03-09 13:28 Jean-Hadrien CHABRAN
2008-03-09 14:45 ` Jean-Hadrien CHABRAN
2008-03-09 17:44 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=61B99676296C5044A1A088C0D0EA1BA801B3C342@syr2k3mail \
--to=dmack@tickets.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox