RE: [Halevt-dev] Can't mount devices for admins in SUM

[Brown, Tony-P56943]

I believe we have discovered what is occurring.  The problem was
happening when the PA inserted the media before logging in. We did, in
fact, get a mount point, it was just not showing up in our halevt
interface program (/usr/sbin/hapHalevt in the script snippet below).
Halevt was started after log in, so this invoked the OnInit rule in our
script.

In our OnInit we had the following:
<halevt:OnInit exec='halevt-mount -u $hal.udi$ -m 002;
/usr/sbin/hapHalevt Add_Init USB "$hal.udi$" "$hal.volume.mount_point$"
"$hal.volume.label$"'/>

When /usr/sbin/hapHalevt was called the mount point was empty.  We also
have a rule for when a mount point is obtained, and hapHalevt is called
there too. But, since hapHalevt will not update its database for a
duplicate device, we didn't update the database when the device did get
a mount point.  The solution was to not call hapHalevt in the OnInit.

<halevt:OnInit exec='halevt-mount -u $hal.udi$ -m 002'/>  //don't call
/usr/sbin/hapHalevt here

Thanks,
Tony


-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf
Of Patrice Dumas
Sent: Sunday, March 21, 2010 12:12 PM
To: address@hidden
Subject: Re: [Halevt-dev] Can't mount devices for admins in SUM

On Thu, Mar 11, 2010 at 04:27:20PM -0700, Brown, Tony-P56943 wrote:
> 
> Once logged in, we want to start halevt on his behalf so he can insert
> some media and archive the audit logs so the system can be recovered
and
> the PU can get back to work.   However, if we start halevt just like
we
> do in runlevel 5, it starts but it mounts no media.  

My first guess is an issue with consolekit. Do you use consolekit?
If so, can you list the PA session? Also you can start halevt on a 
console without going in the background, with the -f option and see 
what it reports.

> If we execute
> without specifying a user, like this: halevt -c
> /etc/hapRMM_B/.halevt/hapHalevtConfigActions.xls it will then mount
the
> media, however, it is owned by root with permissions 775, and the PA
> cannot access the device to write the audit logs.

That looks correct, but indeed, not what you want.

--
Pat