Jorge Castro: Unity Bitesize Bug Status for 19 January


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) Jorge Castro: Unity Bitesize Bug Status for 19 January
# 1  
Old 01-20-2011
Jorge Castro: Unity Bitesize Bug Status for 19 January

I'm a day late due to being sick yesterday, now things are back on track.*

The team is now back from Dallas, Texas, and as OMG!Ubuntu! points out, much has landed after the sprint, a culmination of a week's work of hacking. Neil talks about Unity in this interview. Nice work Joey and Benjamin for covering Unity updates whilst the team flew back home.*

read more



More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

removing application from the unity menu

Hello I have removed wine but the symbols of it application were in the unity menu (though nothing happened when I clicked on them). How can I remove symbols from the unity menu? (1 Reply)
Discussion started by: programAngel
1 Replies

2. UNIX for Advanced & Expert Users

To run the script only if the date is not between 5 th and 10th of january ?

Hi I am new to unix. I have to set up a cron for the program , which should run every Monday at 3 a.m, however , if the date is between the 5 th and the 15th of January,APril or December, the program should not run I know i cant do this in cron , Help with writing the if contion is... (7 Replies)
Discussion started by: saiviren
7 Replies
Login or Register to Ask a Question
GSSAPI::Status(3)					User Contributed Perl Documentation					 GSSAPI::Status(3)

NAME
GSSAPI::Status - methods for handlings GSSAPI statuses SYNOPSIS
use GSSAPI; $status = GSSAPI::Status->new(GSS_S_COMPLETE, 0); if (GSS_ERROR($status->major)) { die "a horrible death"; } if (! $status) { # another way of writing the above die "a horrible death"; } $status = $some_GSSAPI->someop($args1, etc); if ($status) { foreach ($status->generic_message, $status->specific_message) { print "GSSAPI error: $_ "; } die "help me"; } DESCRIPTION
"GSSAPI::Status" objects are returned by most other GSSAPI operations. Such statuses consist of a GSSAPI generic code and, for most operations, a mechanism specific code. These numeric codes can be accessed via the methods "major" and "minor". The standard textual messages that go with the current status can be obtained via the "generic_message" and "specific_message" methods. Each of these returns a list of text which should presumably be displayed in order. The generic code part of a GSSAPI::Status is composed of three subfields that can be accessed with the "GSS_CALLING_ERROR", "GSS_ROUTINE_ERROR", and "GSS_SUPPLEMENTARY_INFO" functions. The returned values can be compared against the constants whose names start with "GSS_S_" if your code wants to handle particular errors itself. The "GSS_ERROR" function returns true if and only if the given generic code contains neither a calling error nor a routine error. When evaluated in a boolean context, a "GSSAPI::Status" object will be true if and only if the major status code is "GSS_S_COMPLETE". When evaluated in a string contect, a "GSSAPI::Status" object will return the generic and specific messages all joined together with newlines. This may or may not make "die $status" work usefully. BUGS
The base objects are currently implmented as a blessed C structure containing the major and minor status codes. It should probably be a blessed array or hash instead, thereby cutting down on the amount of C code involved and making it more flexible. AUTHOR
Philip Guenther <pguen@cpan.org> SEE ALSO
perl(1) RFC2743 perl v5.16.2 2008-02-02 GSSAPI::Status(3)