Displaying 5 results from an estimated 5 matches for "environmn".
Did you mean:
environmnt
2009 Jun 14
2
Permissions of new files on samba with other read on.
...t;I have troubles of global readable bit on new file created on samba.
>I wish to have a 660 permission on new files, instead i've got 664.
>
>also, if i create an empty files it will get 644 permmission, instead of 660.
>
>directory creation instead seems fine.
>
>Below my environmnent and tests.
>pointing to samba docs or bugs, open or closed, are REALLY welcome.
>
>----
>environment:
>Server: Debian Lenny, kernel 2.6.26-2-xen-686, samba 2:3.2.5-4lenny2
>
>Client: Ubuntu Jaunty, kernel 2.6.28-11-generic, smbclient 2:3.3.2-1ubuntu3,
>/sbin/modinfo /lib...
2005 Dec 23
0
RoutingErrors Showing Up in Production Log
I am seeing errors of this type:
ActionController::RoutingError (Recognition failed for "/blah/50112.mp3"):
Showing up in production.log. I''d like to suppress as they are ''known'' and
not real errors.
I have my logging set to:
config.log_level = :error
In environmnent.rb.
What can I do to remove these errors from my log?
Cheers
2009 Jun 12
2
only seeing one NIC in network device editor
Hi,
When I click on "Edit Network" on my managed node in the hosts tab of
the oVirt UI I only see one NIC. My managed node has 2 NICs, one on the
guest network and one on the admin network. The NIC on the admin
network is not listed in the network editor. Is this normal?
I'm trying to create a VM and boot the cobbler profile I created for
Fedora 10 but I can only boot the VM
2009 Aug 08
2
Problem using model.frame with argument subset in own function
Dear List,
I am writing a formula method for a function in a package I maintain. I
want the method to return a data.frame that potentially only contains
some of the variables in 'data', as specified by the formula.
The problem I am having is in writing the function and wrapping it
around model.frame. Consider the following data frame:
dat <- data.frame(A = runif(10), B = runif(10), C
2009 Mar 31
2
Wishlist: optional svn-revision number tag in package DESCRIPTION file
Hi,
just a little wish :
Could we have one (or maybe more) standardized optional tag(s)
for package DESCRIPTION files to cover svn revision info?
This would be very useful for bug reporting...
I know that any developer is already free to append corresponding lines
to DESCRIPTION files to do something of this sort --- e.g. lines like
LastChangedDate: {$LastChangedDate: 2009-03-31 $}