search for: expdate

...e more than 80 hours to complete. Needless to say I am looking for a more elegant/quicker solution. Really need some help here. Here is the issue: I have a dataframe CALL (the dput of head is given below) which has close to a million rows. There are 2 date columns which are of importance, DATE and EXPDATE. There is another dataframe, VOL (dput of head given), which has 2 columns, DATE and VOL. It has the volatility corresponding to each day and it has a total of 124 records (corresponding to 6 months). I want to add another column in the CALL dataframe which would contain the sum of all the volatili...

...; > ... > > AS I said, you can use rpcclient to do this: > > RPCLOOKUPID=$(rpcclient -P -c "lookupnames $USER" dc1) > USERDCID=$(echo "$RPCLOOKUPID" | grep -e '[0-9]\{4,9\} ' -o) > QUERYUSER=$(rpcclient -P -c "queryuser $USERDCID" dc1) > EXPDATE=$(echo "$QUERYUSER" | grep 'Password must change Time' | cut -d > ":" -f 2,3,4,5 | sed -e 's/^[[:space:]]*//') > > If I feed my name into this, I get: > > Thu, 14 Sep 30828 03:48:05 BST > > Which is understandable, because my password is set...

...ect (using sqldf) on a sample dataframe, I could not get a result. But when I use 'subset', I get an output. Below is the sample dataset named 'dlfhead': structure(list(NAME = c("DLF", "DLF", "DLF", "DLF", "DLF", "DLF" ), EXPDATE = structure(c(15001, 15001, 15001, 15001, 15001, 15001 ), class = "Date"), STRIKE = c(280, 280, 280, 280, 280, 280), TMSTMP = c("14:54:17", "14:42:38", "14:09:04", "14:20:25", "12:27:26", "11:59:36"), PRICE = c(22, 23, 23...

Sorry that was easy enough let seconds=`date -d "${EXPDATE}" "+%s"`-`date "+%s"` let days=$seconds/86400 echo $days > /na/homes/$1/.pwd_exp On Fri, Feb 3, 2017 at 11:15 AM, Jeff Sadowski <jeff.sadowski at gmail.com> wrote: > Actually is there a way to show it more like a timestamp. It is hard to > compute days lef...

...nd(:first, :conditions => [ "suppcode = ?" , sdoc.supplier_id]) %> <%= supp.suppname %> </td> <td><%= sdoc.supdesc %><b> /</b><br /> <%= sdoc.rm_id %> </td> <td><%= sdoc.docdate %><br /><%= sdoc.expdate %></td> <td><%= sdoc.doctype.docdesc %> <!-- <% for column in Sdoc.content_columns %> <td><%=h sdoc.send(column.name) %></td> <% end %> --> <td><%= link_to ''Show'', :action => ''show''...

Hi all, I'm trying to install the mixdist package with: install.packages("mixdist") But I'm getting the following errors: * installing *source* package ‘mixdist’ ... ** R ** data ** preparing package for lazy loading ** help *** installing help indices ** building package indices ... Warning in utils::data(list = f, package = package, lib.loc = lib.loc, envir = dataEnv) :

...case something failed or is taking longer then it should. now people get how many days till their password expires. Thank you all so much :-) On Fri, Feb 3, 2017 at 11:22 AM, Jeff Sadowski <jeff.sadowski at gmail.com> wrote: > Sorry that was easy enough > let seconds=`date -d "${EXPDATE}" "+%s"`-`date "+%s"` > let days=$seconds/86400 > echo $days > /na/homes/$1/.pwd_exp > > > On Fri, Feb 3, 2017 at 11:15 AM, Jeff Sadowski <jeff.sadowski at gmail.com> > wrote: > >> Actually is there a way to show it more like a timestamp....

This seems to work for maxPwdAge ldapsearch -LLL -Q -s base -h ad.mydomain.tld -b dc=ad,dc=mydomain,dc=tld maxPwdAge now I just need to query a users pwdLastSetq I tried the commands above but am not getting anything. I tried looking at the ungrepped output but I don't see how to link the pwdLastSet with any user. I get a long list. I think I'm looking for dn: and a matching pwdLastSet?

...CN=System,DC=ad,DC=mydomain,DC=tld > ... AS I said, you can use rpcclient to do this: RPCLOOKUPID=$(rpcclient -P -c "lookupnames $USER" dc1) USERDCID=$(echo "$RPCLOOKUPID" | grep -e '[0-9]\{4,9\} ' -o) QUERYUSER=$(rpcclient -P -c "queryuser $USERDCID" dc1) EXPDATE=$(echo "$QUERYUSER" | grep 'Password must change Time' | cut -d ":" -f 2,3,4,5 | sed -e 's/^[[:space:]]*//') If I feed my name into this, I get: Thu, 14 Sep 30828 03:48:05 BST Which is understandable, because my password is set to never expire. So, unless micr...

...; > ... > > AS I said, you can use rpcclient to do this: > > RPCLOOKUPID=$(rpcclient -P -c "lookupnames $USER" dc1) > USERDCID=$(echo "$RPCLOOKUPID" | grep -e '[0-9]\{4,9\} ' -o) > QUERYUSER=$(rpcclient -P -c "queryuser $USERDCID" dc1) > EXPDATE=$(echo "$QUERYUSER" | grep 'Password must change Time' | cut -d > ":" -f 2,3,4,5 | sed -e 's/^[[:space:]]*//') > > If I feed my name into this, I get: > > Thu, 14 Sep 30828 03:48:05 BST > > Which is understandable, because my password is set...

Hey all, I had asked a question a little while ago about CPU usage being outrageous while using tc and a cbq qdisc. Ed was very kind and offered a few suggestions. One of these was to look at hashing. So after pounding away at it for about a week, I have a general understanding of how it works and have tried to implement it. Unfortunately, and quite obviously since I''m posting here, it